WebSphere Message Brokers
File: au16662_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:46

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.

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

Importing database files after the first import results in unexpected behavior

The import action in the Add Database Table Schemas dialog box is not identical to the action in the Data perspective. Do not use these two import actions interchangeably to the same target folder because unexpected behavior might occur.

Migration to the Version 6.0 Configuration Manager repository is unsuccessful

A migrated Configuration Manager does not start

When the 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

The New Message Definition File menu option does not appear after you have migrated your workspace from Version 5.1

You encounter problems when you try to connect to a migrated Configuration Manager from Message Broker Toolkit Version 6.0

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:46

au16662_ This topic's URL is: