Migration limitations in Maximo II

Migration limitations

Even though most of the content configuration can be migrated in most environments, some of them cannot be migrated. For these configurations extra steps are required in some circumstances for migration. They are listed as follows:

Different database platforms

A package cannot be migrated between different database platforms if it contains configuration records for objects, attributes, keys, indexes, or sequences. Migration Manager issues an error message indicating that it cannot deploy such type of package. For confirming the causes of the error, have a look at the manifest of the package. View the manifest for determining whether the DMMAXOBJECTCFG migration object is part of the package or not?

Electronic auditing

Migration of any electronic auditing tables could not be done, if you use the Database Configuration application to enable electronic auditing.

Exchange rates

Migration of exchange rates is possible only if the application servers in the source and target environments are configured to use the same time zone. In two different time zones, a package might not be deployed because of overlapping exchange rate validity periods. You cannot use exchange rates that have overlapping validity periods.

Discarded configuration changes

A Change package can listen for database configuration events that occur in the Database Configuration application. Event information (inserts, updates, deletes) are persisted in the event tracking table. If a user discards all the database configuration changes by using the Discard Configuration Changes action, the events that are already captured remain in the tracking table. A migration user might not be aware that the events remain in the tracking table and might proceed to create, distribute, and deploy a package.

Lookup maps

When lookup maps are migrated for new business objects, the migration of a single package that contains both the lookup map records and the business object records will be failed. The migration fails because the lookup map is processed first and depends upon the business object, which is not processed yet.

Integration tables

Changes to the Integration module interface tables, default queue tables MXIN_INTER_TRANS and MXOUT_INTER_TRANS, and any customized queue tables are not migrated. If any configuration changes are done in the source database to these tables, same changes must be done in the target database.

User and person records

If a person’s record and its related user record are inactive, a deployment error occurs. The person record must be active for it to be added to a user record. To work around this limitation, first migrate the person records. Now activate them in the target environment, and then migrate the user records. Error resolved!

Organizations

After deployment of a package, a newly created organization in a target environment is inactive. It is because; a newly created organization cannot be activated without clearing account (GL). The association of a GL account with an organization is a manual post-deployment step.

System XML files

Migration Manager does not support migration of user interface system XML files between product environments. System XML files include lookups.xml, menus.xml and library.xml. These XML files are not application-specific. They store common user interface components or resources. Use the Application Designer application to manage the export and import of these system XML files.

Restricted attributes

If an attribute is restricted by the Database Configuration application in a target environment, and an override of the restriction is not set up at the object structure level, the value of the attribute is not deployed.

Start centers

Only the start center templates can be migrated. After you migrate a start center template, you can apply the template to an appropriate start center.

MAXVARS Table

The source and target environments must have identical MAXVARS tables. Ensure that you use the same installation and upgrade procedures in the environments so that the tables are identical.