Troubleshooting
Problem
This technote details an error that can occur when listing the metadata types from an IBM® Rational® ClearCase® VOB on Microsoft® Windows®, Linux® or UNIX®.
Cause
Attempts to run the command string cleartool lsvob -kind lbtype -invob <vobtag> results in the following error:
cleartool lsvob -kind lbtype -invob /vob/with/problem
lbtype1
cleartool: Error: INTERNAL ERROR detected and logged in
"/var/adm/rational/clearcase/log/error_log".
lbtype3
cleartool: Error: INTERNAL ERROR detected and logged in
"/var/adm/rational/clearcase/log/error_log".
lbtype5
In the above example, the error is happening because the local copy of a global type points to a nonexistent global type. Meaning, there is a reference (or link) from a local copy that still points to a global type that was removed.
Resolving The Problem
The following steps outline how to verify that you are seeing this problem and how to resolve the errors. You will need to remove the references from the local copy to the global type that no longer exist, and then recreate the global type.
Note: There are specific considerations for replicated VOBs that are detailed below.
- Run cleartool lstype -short -local -kind lbtype -invob <vob/with/problem>
Note: The -local switch is used.
You will see something like this in the first output:
lbtype1
lbtype2
lbtype3
lbtype4
lbtype5
- Run cleartool lstype -short -kind lbtype -invob <vob/with/problem>
You will see something like this in the second output:
lbtype1
cleartool: Error: INTERNAL ERROR detected and logged in
"/var/adm/rational/clearcase/log/error_log".
lbtype3
cleartool: Error: INTERNAL ERROR detected and logged in
"/var/adm/rational/clearcase/log/error_log".
lbtype5
- Compare the first and second outputs from steps 1 and 2 above. The types with the error should coincide with the ones missing from the list. From the above examples, the errors are reported for label types, lbtype2 and lbtype4.
- If the AdminVOB and the client are not replicated, then run cleartool checkvob -hlinks against the problem label types and then reassociate them with the AdminVOB.
cleartool checkvob -hlinks lbtype:lbtype2
cleartool mklbtype -global -acquire -c "Replaced missing lbtype" {missing lbtype name}@<AdminVOB-tag>
- If the AdminVOB is replicated, confirm if the problem happens at the other sites where these VOBs are replicated.
- If the problem does not happen, then you have a divergence in the AdminVOB replica and will need to replace it. Refer to your IBM Rational ClearCase Multisite Administration Guide for direction on replacing a replica.
- If the problem does occur at all sites, then use the following commands to resolve the problem:
- Run cleartool checkvob -hlinks lbtype:<problem lbtype> against the problem lbtypes.
- Synchronize with all sites to ensure the problem lbtypes no longer have a hyperlink reference to the AdminVOB by running the original lstype command; no error should occur. Once confirmed, proceed to the next step.
Note: If the problem label type still has a reference to the AdminVOB, you will need to run cleartool checkvob -hlinks lbtype:<problem lbtype at each site before proceeding.
- Create new label types in the AdminVOB with the same name as the problem ones as follows:
cleartool mklbtype -global -acquire -c "Replaced missing lbtype" {missing lbtype name}@<AdminVOB-tag>
Related Information
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21217204