Tip: Need to specify old version when upgrading from JTS, CCM or RQM 3.0.1.1 M3 to 3.0.1.1 GA
Heather Sterling
Last Updated: October 10, 2011
Build: Rational Quality Manager 3.0.1.1, JTS 3.0.1.1
Summary
If you upgrade JTS, CCM, or RQM from 3.0.1.1 M3 to 3.0.1.1 GA, you need to explicitly specify a different value for the oldJTSVersion and oldApplicationVersion arguments in the upgrade script commands.
More Information
JTS Upgrade
Error details: If you fail to specify the oldJTSVersion flag, you will get the following error when upgrading the JTS from 3.0.1.1 M3 to 3.0.1.1 GA:
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.
Workaround: Explicitly specify the oldJTSVersion flag with a value of 3.0.1 even though 3.0.1 is not the version you are upgrading from.
Note: There will be NO functional impact by specifying 3.0.1 instead of 3.0.1.1 but this workaround is needed for the upgrade to proceed.
CCM and RQM Upgrades
Error details: If you fail to specify the oldApplicationVersion flag, you will get the following error when upgrading the application from 3.0.1.1 M3 to 3.0.1.1 GA:
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.
Workaround: Explicitly set the oldApplicationVersion flag with a version of 3.0.1.
Note: There will be NO functional impact by specifying 3.0.1 instead of 3.0.1.1 but this workaround is needed for the upgrade to proceed.