Workaround: Upgrading from a CLM server version 3.0.1.4 or above to CLM version 4.0 or 4.0iFix1 (4.0.0.0.1) results in an error

Summary

Upgrading from a Rational solution for Collaborative Lifecycle Management  (CLM) version 3.0.1.4 or above to CLM version 4.0 or 4.0iFix1 (4.0.0.0.1) may result in the following errors:

CRJAZ2124E The old JTS version could not be determined.  Verify that the oldJTSHome is pointed at the correct installation and  specify the version using the oldJTSVersion parameter.    CRJAZ2123E The old application version could not be determined.  Verify that the oldApplicationHome is pointed at the correct  installation and specify the version using the oldApplicationVersion  parameter.

This will prevent upgrade from continuing even though the upgrade is supported.

More Information

Problem

CLM versions 4.0 and 4.0iFix1 (4.0.0.0.1) do not correctly detect CLM versions 3.0.1.4 and above as supported versions for upgrade.

Workaround

The version of the JTS or application to be upgraded can be specified as 3.0.1.3. This will allow upgrade to continue.

  1. Add the parameter -oldJTSVersion=3.0.1.3 when running jts_upgrade
  2. Add the parameter -oldApplicationVersion=3.0.1.3 when running upgrade for the application (ccm_upgrade, qm_upgrade, rm_upgrade).

Related Information

The following links point to related information:


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 2 people rated this as helpful.