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 have been migrated from Version 2.1 cannot resolve subflows

A broker has been migrated from Version 2.1 to Version 6.0 and some message flows are now stopped

Deployment of message flows fails when you migrate them from Version 2.1 to Version 6.0

Error messages are issued after a Version 2.1 broker is migrated to Version 6.0

Start of change

The mqsimigratecomponents command fails with database error BIP2322

End of change

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.

Migration to the Version 6.0 Configuration Manager repository is unsuccessful

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