The following sections describe how to fix problems that occur during import of a replica-creation packet.
When you use the –preserve option with mkreplica –import, import of a replica-creation packet fails if the identity of the user importing the packet does not have rights to create source container files with particular groups. To fix this problem, do one of the following things:
A recoverable error occurs if the mkreplica –import command detects a conflict at the registry level because an entry exists in the object registry:
A conflict in the registry can occur if a mkreplica –import commands fails and removes the VOB storage directory but not the registry entry. Verify that cleartool lsvob does not report any VOB storage directory at the location you specified with the –vob option. In this case, the object registry contains an entry with no corresponding VOB tag. For example:
cleartool lsvob –storage /net/goldengate/vobstg/dev.vbs cleartool: Error: Unable to access "/net/goldengate/vobstg/dev.vbs": No such file or directory. cleartool: Error: Versioned object base not found: "/net/goldengate/vobstg/dev.vbs". cleartool: Error: No vob tags found for vob "/net/goldengate/vobstg/dev.vbs".
Restore the registry to a consistent state by following these steps:
Caution: Do not edit the information in the registry file directly.
A recoverable error occurs if the mkreplica –import command detects a conflict at the registry level because an entry exists in the tag registry:
mkreplica –import may be able to create and register the VOB storage directory, but may find that the specified VOB tag is already in use. In this case, create another VOB tag for the new VOB storage directory with a cleartool mktag command or with the ClearCase Administration Console (available on Windows).
You do not have to reenter the mkreplica –import command in this case. You can delete the replica-creation packet from disk storage (if appropriate).