Migrating change requests from development databases in the central CR database

The CR migrate can take a long time to complete, sometimes hours or even days for large databases. Also, any DCM packages received while CR migrate is in progress can dramatically extend this time.

Procedure

  1. Back up your databases.

    Ensure that you have a full backup of your central CR database and the development database that you want to migrate.

  2. Log on to the Admin interface.

    If you have one or more remote servers, log on to the server that manages the development database from which you want to migrate.

  3. Open the CR Migrate dialog box.
    1. On the Action Panel, click the System Administration link.
    2. Click the Admin tab.
    3. In Properties, click CR Migrate.
  4. Select the database to migrate.

    All of your development databases managed by this server are listed in a menu. Select the database containing the CRs you want to migrate.

  5. Optionally, type an email address.

    Since migration can take a long time, you can request email notification of its completion. If your central server is configured to send email through an SMTP server, check the Email When Done option. If your email address is incorrect, type the correct address.

  6. Start migrating change requests.

    Click Migrate. If no errors occur, the CR migrate continues without any further intervention.

  7. During the migration, use the CR Migrate dialog box to monitor its progress.

    Closing the dialog box does not stop the migration.

    • Reopen the CR Migrate dialog box at any time to check its current progress.
    • To stop the migration, click Stop. You can restart the migration later by migrating the same database again. IBM® Rational® Change resumes from where you last stopped. A migration can also be resumed when it fails midway due to a network problem or other error.
    • Users can use Rational Change during a CR migrate. Both the central CR database and the development database can remain enabled. As CRs are migrated into the central CR database, they are immediately available for users to view and edit, even before the entire migrate is complete. The newest CRs are transferred first.
  8. After the CR migrate has finished, run the ccmdb update_statistics command to optimize your central CR database.
    • The ccmdb update_statistics command can be run in the middle of a CR migrate.
    • If you suspect the migration is getting slower as it progresses, running this command in the background might improve performance.

Feedback