Migration limitations in Maximo I

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:

Actions

For migrating a WFINITIATE action, which is used for the initiation of a workflow process, the workflow process must be active. For this to happen two deployments are required. Migrate the workflow process and activate it in the target environment first, and then migrate the action.

Action groups

For migrating action groups that are created in the Actions application, there is a need of migrating all the actions that are in each action group. If the actions are not migrated, the action groups cannot be used in the target environment.

Base language

A target environment must have the same base language as the source environment. If the target base language is different from the source base language, packages cannot be deployed.

Collection restrictions

Talking about these Collection restrictions, here the Data restrictions for objects and attributes are migrated, but collection restrictions are only migrated partially. Clearly to say, Data in the SECURITYRESTRICT table is migrated. Data in the COLLECTIONAUTH table is not migrated.

Crossover domains

For the migration of this crossover domain to which an attribute has been added, creating and deploying of two packages are must. Deploying the first package, it must have the attribute but not the domain. The second package to deploy must contain the domain.

Database configuration

In Oracle databases, setting up a system to run with a login user name that is different from the schema owner is a complex manual task and might cause migration errors. To avoid these types of errors, make ensure that the system properties mxe.db.user and mxe.db.schemaowner contains the same value.

Database indexes

For IBM DB2 databases, the indexes may not be migrated. If a package is deployed and an index exists in the target environment, then the index in that package is not deployed. The index is created manually, if it is not existed in the target environment. If the index in the package is marked to be deleted, the index in the target with the same table and attribute combination should be marked to be deleted.

Classifications

The following limitations affect the migration of classifications:

• The Data which is related to the CLASSIFICATION table is not migrated.
• In Snapshot packages, regardless of the selected processing action, a database update is performed for classification records.
• You cannot migrate a classification hierarchy in which a parent classification was changed to alter the parent-child classification relationship.
• You cannot migrate two or more different classifications that contains the same hierarchy path.