r3 - 2013-11-06 - 10:02:33 - PaulEllisYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > UpgradingRequirementsComposerFrom2To3

under constructionAdvanced Upgrade observations: IBM Rational Requirements Composer 2.x to 3.x

Authors: ShirleyHui
Build basis: CLM 2011, Rational Team Concert 3.0.1, Rational Requirements Composer 3.0.1

This article describes details specific to migrating from Rational Requirement Composer (RRC)2 to RRC3, also known as CLM 2011.
Refer to Upgrade Reference for CLM 2011 for overall guidance on upgrading.
This article is also relevant to those who wish to migrate to RRC 4.x/CLM 2012 and beyond, as the migration to 3.x is a first step in the two-step process of migrating from RRC 2.x.


  • Migrate using the most recent version of 3.0.1.x in order to have the most up to date fixes in migration code. Currently this is version RRC
  • Validate the data after migrating to and BEFORE proceeding with an upgrade to 4.x or newer versions.

Please use the following sections to understand the data migration, and to plan and execute your migration.


  • The migration occurs for the entire RRC2 repository. Partial or project-by-project migration is not supported.
  • Migration of RRC2 project archives is not supported.
  • All URI references using the rich-client based protocol (rpc://protocol) will be broken after migration.
  • This protocol is not supported in RRC3.

Perform backups

Migration cannot be resumed or restarted if an error is encountered. You must restart the migration at the previous step from backup. Perform a backup of the Jazz Team Server and database (this includes the database and the InstallDir/server/conf directory) before:

  • Running the upgrade\rm_upgrade.bat script (offline migration step)
  • Starting the online migration

Online migration error handling

The online migration phase must run uninterrupted from start to finish.

Fatal error conditions:

  • Loss of connectivity to JTS.
  • Insufficient disk space.
  • General environment failures, such as power failure or other network issues.

If you encounter any of these fatal errors, resolve the environment issues, restore the Jazz Team Server server from backup and run the online migration again.

Unexpected migration error

When the online migration is complete, it will report whether it was successful.

If it reports that the migration failed, locate the 'migration-errors.log' in InstallDir/conf/rdm/migration/systime-tmp directory. systime is a 13 digit number based on the time the migration ran.

Review the errors for conditions related to the environment (network, JTS error). If possible, correct the condition, restore from backup, and run the online migration again.

If there are no environment failures, contact IBM Support.

Errors in individual resources

The online migration will be successful even if there are errors in individual resources. These errors are not considered fatal. You will be able to access the repository to validate the migration.


We highly recommend that you perform a trial upgrade in a test environment before upgrading your production environment. Errors in individual resources should be investigated to determine if the migration code can be corrected. Often, the resource was corrupted in RRC2 and is no longer in use in your project.

Related topics: Limitations, Understanding the data transformations, Running a trial migration, Perform backups before offline and online migration steps, Online migration error handling, Review the migration results

External links:

Additional contributors: PaulEllis

Topic attachments
I Attachment Action Size Date Who Comment
Jpgjpg migrationWithErrors.JPG manage 57.5 K 2013-10-03 - 16:36 PaulEllis  
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.