Resolving problems when migrating or importing other resources

This topic contains advice for dealing with some common problems that can arise when you import or migrate resources other than message flows.

Error messages are issued after you migrate a Version 2.1 broker

The mqsimigratecomponents command fails with database error BIP2322

The File > Import menu provides only the option to import a compressed file inside an existing project

The source directory name contains spaces

Migration to the Version 6.0 Configuration Manager repository is unsuccessful

A migrated Configuration Manager does not start

When the Version 6.0 Configuration Manager has started successfully, the following event messages appear in the system's local error log with the source identifer WebSphere Broker v6000: 2001, 1223, 1224, 1228, 8255, 8280, and 1003.

If the error log still contains the original six event identifiers repeatedly (2001, 1223, 1224, 1228, 1205, and 1007), repeat steps 1 to 3, increasing the value that is assigned to the APP_CTL_HEAP_SZ parameter.

You redefined a broker in a migrated Configuration Manager and used the Configuration Manager Proxy to modify the broker reference's UUID

You encounter problems when you try to connect to a migrated Configuration Manager from Message Brokers ToolkitVersion 6.0

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:41:18

au16662_