r29 - 2015-07-24 - 17:56:49 - DianeEverittYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > KnownIssues

Items to consider before upgrading

Authors: UpgradeTroubleshootingTeam
Build basis: CLM 4.x, CLM 5.x

Before upgrading, it is important to consider known issues on each version to validate if this will cause any issues.

Items to consider before upgrading

It is important to understand the defects associated with your deployment that might not be resolved or included in the version you are upgrading to. Ensure that this will not affect your users after you upgrade.

Defects fixed in specific product release

Below is a list of queries you can run on Jazz.net to validate which defects were resolved in the latest releases.
  Rational Team Concert Rational Quality Manager Rational DOORS NG Rational Jazz Foundation
APAR related Defects resolved in the release

Non-APAR related Defects resolved in the release


For defects resolved in other versions, check the release notes for that particular release.

Rational Team Concert Rational Quality Manager Rational Requirements Composer/ Rational DOORS NG

Known issues

Known issues when upgrading to 4.0.1 or later

Incorrect indexes in 4.0.1 (resolved in 4.0.2)

There is a known defect with indexes upon upgrading to 4.0.1 as identified in Technote 1620879: Upgrades to 4.0.1 create a significantly larger, incorrect index. A Testfix is required before upgrading, but this defect has been resolved in version 4.0.2. Upgrade to the latest release of the Rational solution for Collaborative Lifecycle Management (CLM) to ensure that defects to all known issues have been resolved.

Upgrade Scripts fail with Microsoft SQL Server and CLM Upgrade to 4.0.4 (resolved in 4.0.5)

There is a known issue where the upgrade scripts will fail during an upgrade to CLM 4.0.4. This is documented in Technote 1649768: Upgrading CLM products to version 4.0.4 fails when using Microsoft SQL Server. This defect has been resolved in version 4.0.5.

Work Items can not be loaded in RTC web client after upgrade to CLM 4.0.5 and above (resolved in 5.0.2)

After upgrading to CLM 4.0.5 or above, some Work Items can not be loaded in RTC web client. This problem only occurs in the web client and is caused by too many attributes in the Work Item type. This is due to the change made to the way to batch value sets starting in version 4.0.5. This defect has been resolved in version 5.0.2.

Known issues when upgrading to 5.0 or later

All Project Areas are deleted after upgrade from RRC or RDNG release 4.0.x

There is a known defect that all project areas are deleted upon upgrading RRC or RDNG 4.0.x to 5.0.x. Refer to Technote 1695623: All Project Areas are deleted after upgrade from RRC or RDNG release 4.0.x for more information.

LPA templates may not be retrieved after an upgrade to 5.0.2 (fixed in 5.0.2 iFix002)

There is a known defect affecting sites where a server rename was performed on the upgrade server before being upgraded to CLM 5.0.2 as described in Technote 1693288: CLM LPA templates may not be retrieved after a migration from older release to 5.0.2. The defect has been resolved in version 5.0.2 iFix002.

Known Workarounds

Known workarounds when upgrading to 4.0.7 or later are discussed below.
  Rational Team Concert Rational Quality Manager Rational Requirements Composer Rational Jazz Foundation
Documented Workarounds

Related topics:

External links:

  • IBM: None

Additional contributors: StephanieBagot, DianeEveritt

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r29 < r28 < r27 < r26 < r25 | 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.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project