Troubleshooting
Problem
This technote explains why rebasing an IBM® Rational® ClearCase® UCM stream fails with, []Unable to resolve VOB symlink "link.oid" -> "..\link" component "link": No such file or directory.[], along with directions to resolve the error.
Symptom
When rebasing a development stream, this error appears:
Unable to resolve VOB symlink "virt.46e5e94ff9024144ab0fe9ed432ce6e6" -> "..\virt" component "virt": No such file or directory.
Cause
ClearCase is seeing a broken link, virt.46e5e94ff9024144ab0fe9ed432ce6e6 , as a VOB object that it cannot completely resolve.
A cleartool ls from the command prompt will show:
virt.46e5e94ff9024144ab0fe9ed432ce6e6 --> ../virt
virt.5043bcc7c8f44439938d634bd5ba9ac2 --> ..virt [not loaded]
The above symbolic link is to a resource outside of ClearCase, which renders the hyperlink invalid for use in UCM.
Resolving The Problem
Remove the broken (dangling) link from the VOB to clear the error, using the cleartool rmname command . Then the rebase operation will process without reporting the above error.
Example:
cleartool rmname virt.46e5e94ff9024144ab0fe9ed432ce6e6
Using cleartool rmname allows you to preserve the symbolic link, but remove references
to it from future directory versions. Symbolic links can be permanently removed using cleartool rmelem, refer to technote 1148781 for more details.
Related Information
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21125166