You must have a Version 6.0 installation of the product with the required component code installed, that is, the broker component is installed if it is needed, and so on.
Before starting migration, stop any debugging sessions in the Control Center. It is not possible to migrate message flows that are being debugged.
1> use master 2> go 1> sp_dboption "BROKER1","ddl in tran",TRUE 2> go Database option 'ddl in tran' turned ON for database 'BROKER1'. Run the CHECKPOINT command in the database that was changed. (return status = 0) 1> use BROKER1 2> go 1> checkpoint 2> gowhere BROKER1 is the name of the Sybase broker database.
The migration check can be run against a running component, or set of components. This does not impact the components, except for imposing a slight performance penalty. Note that on UNIX systems, the odbc.ini file needs to be migrated (that is, a new-format odbc.ini file needs to be created with the same set of data sources as the old one) before the check can be run, because the checking command needs to be able to access the broker database.
The check command either succeeds or fails, and prints a message about whether or not the migration should succeed, but no modifications are made during the process.
This command can produce a large number of possible responses, depending on the results of the various operations. Note that this command differs from other commands in the way it produces messages – they are displayed as needed, rather than being produced in a batch at the end of the program.
The following example checks for migration of BROKER1 from V2.1 to Version 6.0:
mqsimigratecomponents –c BROKER1 BIP 0001I: Starting migration check for component ‘BROKER1’ to FAD level ‘3’ BIP 0002I: ‘BROKER1’ is version 2.1 (auto-detected) BIP 0003I: Broker database ‘BKRDB’ and schema ‘WMQIUSER’ are not shared with other components. BIP 0004I: No invalid rows found in broker database. BIP 0005I: Migration check passed. BIP 8071I: Successful command completion.
The following example does automatic migration of BROKER1 from V2.1 to Version 6.0:
mqsimigratecomponents BROKER1 BIP 0001I: Starting migration check for component ‘BROKER1’ to FAD level ‘3’ BIP 0002I: ‘BROKER1’ is version 2.1 (auto-detected) BIP 0003I: Broker database ‘BKRDB’ and schema ‘WMQIUSER’ are not shared with other components. BIP 0004I: No invalid rows found in broker database. BIP 0005I: Migration check passed. BIP 0020I: Starting registry migration for component ‘BROKER1’. BIP 0021I: Created top-level ‘CurrentVersion’ key BIP 0021I: Created ‘DSN’ subkey BIP 0022I: Created ‘HTTPListener’ subkey BIP 0023I: Created ‘HTTPListener.HTTPConnector’ subkey BIP 0024I: Created ‘FADLevel’ value; set to ‘3’ BIP 0025I: Created ‘converters’ value; set to ‘’ BIP 0028I: Moving registry data into ‘CurrentVersion’. BIP 0029I: Moved value ‘AdminAgentPID’. [repeat for each value] BIP 0030I: Completed moving registry data into ‘CurrentVersion’. BIP 0025I: Finished registry migration for component ‘BROKER1’. BIP 0011I: Starting database table migration for ‘BKRDB’.’WMQIUSER’. BIP 0012I: Moving table ’BROKERRESOURCES’ to ’somethingBROKERRESOURCES’. BIP 0013I: Creating new table ’BROKERRESOURCES’. BIP 0014I: Copying data from ‘somethingBROKERRESOURCES’ to ’BROKERRESOURCES’. BIP 0015I: Successfully copied all data (322 rows). [repeat for each table] BIP 0016I: Finished database table migration for ‘BKRDB’.’WMQIUSER’. BIP 0017I: Starting queue migration for ‘BKRQM’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.AGGR.CONTROL’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.AGGR.REPLY’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.AGGR.REQUEST’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.AGGR.TIMEOUT’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.AGGR.UNKNOWN’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.TIMEOUT.QUEUE’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.WS.ACK’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.WS.INPUT’. BIP 0018I: Creating new queue ‘SYSTEM.BROKER.WS.REPLY’. BIP 0026I: Clearing queue ‘SYSTEM.BROKER.ADMIN.QUEUE’. BIP 0026I: Clearing queue ‘SYSTEM.BROKER.EXECUTIONGROUP.QUEUE’. BIP 0026I: Clearing queue ‘SYSTEM.BROKER.EXECUTIONGROUP.REPLY’. BIP 0026I: Clearing queue ‘SYSTEM.BROKER.IPC.QUEUE’. BIP 0019I: Finished queue migration for ‘BKRQM’. BIP 0005I: Migration succeeded for component ‘BROKER1’. BIP 8071I: Successful command completion.
The following example is a repeat of the preceding example, but with the -q flag specified:
mqsimigratecomponents -q BROKER1 BIP 0001I: Starting migration check for component ‘BROKER1’ to FAD level ‘3’ BIP 0002I: ‘BROKER1’ is version 2.1 (auto-detected) BIP 0005I: Migration check passed. BIP 0020I: Starting registry migration for component ‘BROKER1’. BIP 0025I: Finished registry migration for component ‘BROKER1’. BIP 0011I: Starting database table migration for ‘BKRDB’.’WMQIUSER’. BIP 0016I: Finished database table migration for ‘BKRDB’.’WMQIUSER’. BIP 0017I: Starting queue migration for ‘BKRQM’. BIP 0019I: Finished queue migration for ‘BKRQM’. BIP 0005I: Migration succeeded for component ‘BROKER1’. BIP 8071I: Successful command completion.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an26150_ |