Troubleshooting failures in change request migration

Use this topic to help you troubleshoot change request migration failures. This topic contains information about some common issues that can occur during the migration and provides possible solutions.

CR migration failed

If CR migration fails because of a transient problem, such as a network failure or a server restart, migrate the failed database again. IBM® Rational® Change continues the process where the failure occurred. CRs that were already migrated are preserved.

If the failure is not self-correcting, see the log files for more details. CR migrations use IBM Rational Synergy DCM technology to migrate your CRs. In many cases, the Rational Synergy and DCM-related logs contain the most detailed information. The ccm_ui.log files for your Rational Change servers often describe failures in enough detail to resolve them. For even more details, including listings of every migrated CR, see the detailed DCM logs, which are in the database dcm/log directories. Depending on when the failure occurred, you might consult the logs in either your development or central CR database.

Not all the databases are DCM compatible

A few DCM compatibility checks can be disabled during CR migrate, specifically the checks for compatible version delimiters and release delimiters. If you are already running in a DCM environment where these checks can be safely ignored, disable them by creating the following file in your Rational Change central server installation area:

For example: CHANGE_APP_HOME/WEB-INF/wsconfig/system/app.user.properties

Then add the following lines as necessary, and restart Rational Change to apply the changes.

migrate_ignore_version_delimiter = true

migrate_ignore_release_delimiter = true


Feedback