Conflict in object registry

A recoverable error occurs if the mkreplica –import command detects a conflict at the registry level because an entry exists in the object registry.

About this task

For example:: 
Replica replica-name already exists
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".

Procedure

  1. In the VOB object registry file, find the incorrect entry for the VOB storage directory pathname you specified. This file is located on the network's registry server host in /var/adm/hcl/versionvault/rgy/vob_object on Linux® and the UNIX® system or versionvault-home-dir\var\rgy\vob_object on Windows®.

  2. Using the UUID in this entry, enter a cleartool unregister –vob –uuid command to remove the incorrect entry.
    Attention: Do not edit the information in the registry file directly.
  3. With the registry restored to a consistent state, reenter the mkreplica –import command.
  4. After the mkreplica command succeeds, delete the replica-creation packet from disk storage (if appropriate).