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
- 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.
- 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.
- Open the CR Migrate dialog
box.
- On the Action Panel, click the System
Administration link.
- Click the Admin tab.
- In Properties,
click CR Migrate.
- 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.
- 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.
- Start migrating change requests.
Click Migrate.
If no errors occur, the CR migrate continues without any further intervention.
- 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.
- 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.