Troubleshooting
Problem
This technote identifies an issue that can occur in IBM Rational ClearCase where a full baseline fails to label a single version of each element visible in a UCM component.
Symptom
Users may notice the following:
- View selection rules are selecting version /main/0 of a directory or file element.
- Not all elements are receiving a label when a baseline is created.
- Only files with changes made after the last baseline creation receive a label when a full baseline is applied.
Cause
This issue has been identified as a product defect under APAR PK95682.
Environment
This defect has only been observed in environments with Clients running a cleartool mkbl at a higher patch level than the VOB servers. The defect indicates that running a cleartool mkbl from a client that has a ClearCase version that is at or later than 7.1.0.1 or 7.0.1.3 or 7.0.0.5 installed against a VOB server that has a ClearCase version earlier than 7.1.0.1 or 7.0.1.3 or 7.0.0.5 will encounter this defective behavior.
You should look into upgrading your VOB server or downgrading your clients to avoid the issue.
Resolving The Problem
Defect APAR PK95682 has been resolved in ClearCase 7.0.0.8 iFix01, 7.0.1.7 iFix01 and version 7.1.1.
WORKAROUND
The bad baseline can be repaired from the VOB server from the command line. The issue appears to be ClearCase version sensitive. To repair the bad baseline, you must repair the label type associated with the baseline. This can be involved if the baseline has successors.
Contact IBM Rational Client Support for information about a workaround providing the following details:
- Operating system and ClearCase version installed on the VOB server
- Operating system and ClearCase version installed on the ClearCase client that created the baseline
Related Information
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21402557