Resolving problems when migrating or importing resources

This topic contains advice for dealing with some common problems that can arise when importing or migrating resources:

The mqsimigratemsgflows command gives unexpected results

Message flows that refer to a migrated user-defined node have connection errors

After migration, message flows cannot locate a user-defined node

The mqsimigratemsgsets command gives unexpected results

You get import problems with imported message sets

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 this causes unexpected behavior.

A migrated Configuration Manager does not start on Windows when using DB2

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.