Troubleshooting
Problem
This technote identifies an error, More than one version with label of type, that can occur in IBM Rational ClearCase due to a defect that causes multiple versions of the same element to be labeled unexpectedly.
Symptom
When browsing a UCM directory within a component from a stream, the ClearCase Explorer crashes with the error:
Windows - Fatal Application Exit
mvfs: error in the configuration specification for view myview_int see the vobrpc_server_log on host
myhost for details.
Also creating baselines or upgrading existing baselines to fully labeled (cleartool chbl -full) fail with the error:
"More than one version with label of type "mybaseline" "
When inspecting the vobrpc_server_log after trying to access the directory it shows:
"More than one version with label of type "mybaseline" "
After modifying or creating baselines, the following error is logged in the db_server log:
db_vista_error -3 (errno=="Resource temporarily unavailable")
DBMS error in /vobstore/myvob.vbs/db
DBMS error in "../db__label.c" line 71
Cause
A baseline label had been applied twice to the same element unexpectedly.
This issue has been identified as a product defect under APAR PK95411.
This defect was introduced in ClearCase versions 7.0.0.5, 7.0.1.3, 7.1.0.1.
It can also be caused by incorrect usage by manually applying a label to an element.
Environment
The defect will occur in situations where the label is applied from a client that is running at a later patch level than the VOB server.
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.
Diagnosing The Problem
Running a cleartool find in the problematic component VOB should show the element labeled twice.
An example of such a command:
cleartool find . -element "lbtype_sub(<label name from error>)"
Resolving The Problem
Defect APAR PK95411 has been resolved in ClearCase 7.0.0.8, 7.0.1.7 and 7.1.1
When the problematic element is found, use cleartool rmlabel to remove the incorrectly placed label. This assumes you know which version of the element should not have received the incorrect label. You might also consider removing the baseline and recreating from the VOB server. The baseline might be in use by other streams. If a baseline is in use, it can not be removed. The label type for that baseline should be regenerated from the VOB server. Contact IBM Rational Client Support if necessary to assist in regenerating the label type from the VOB server.
WORKAROUND
- You should look into upgrading your VOB server or downgrading your clients to avoid the issue.
Refer to technote 1265307 Available iFixes and Fix Packs for ClearCase Family 7.x for a list of available patches.
- Run the make baseline commands directly from the VOB server.
To repair the damaged baseline you will need to remove the baseline associated label and upgrade the baseline label status. Contact IBM Rational Client Support for further assistance 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
swg21402608