10.2 Replica-Creation Problems

Problems with replica creation can occur during the export phase or the import phase.

Export Phase

If the mkreplica -export command finds that a replica with the specified name exists in the VOB family (Replica replica-name already exists), select another name for the new replica, and reenter the mkreplica -export command.

If mkreplica -export -fship fails while it is transporting the packet, it does not remove the new replica's replica object at the creating site. To complete the replica creation, use shipping_server to transfer the replica-creation packet.

Import Phase

A recoverable error occurs if the mkreplica -import command detects a conflict at the ClearCase registry level-an entry exists in the VOB object registry or in the tags registry:

Replica replica-name already exists

Conflict in VOB 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 VOB 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:

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/atria/rgy/vob_object on UNIX or ccase-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.

CAUTION: 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).

Conflict in VOB-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).