IBM Support

A replica cannot update itself

Technote (troubleshooting)


This technote explains why the error multitool: Error: A replica cannot update itself might occur when using IBM® Rational® ClearCase MultiSite® commands.


When running the multitool syncreplica -export command specifying a target replica the following error is reported:

multitool syncreplica -export -ship replica:replica-name
multitool: Error: A replica cannot update itself


local-host:M:\def1\dmm>multitool syncreplica -export -ship original
multitool: Error: A replica cannot update itself


The replica name specified in the syncreplica -export command is believed to be on the local host which may be due to either of the following:

Scenario 1:
The replica might have been created with the wrong replica name.

Scenario 2:
The wrong replica name (name of the local replica itself) was mistakenly specified in the syncreplica -export command.

Diagnosing the problem

Run the multitool lsreplica -long command in the exporting replica VOB.
Note the replicas listed and their hostnames.


local-host:M:\def1\dmm>multitool lsreplica -long
For VOB replica "\dmm":
replica "original"
 2007-08-27T16:33:25-04 by userA (userA.user@local-host)
 replica type: unfiltered
 master replica: original@\dmm
 request for mastership: disabled
 owner: WINDOMAIN\userA
 group: WINDOMAIN\user
  host: "local-host"
  identities: preserved
 permissions: preserved
 feature level: 5
 connectivity: connected
replica "scII-dmm"
 2007-10-16T13:59:57-04 by userA (userA.user@local-host)
 replica type: unfiltered
 master replica: original@\dmm
 owner: WINDOMAIN\userA
 group: WINDOMAIN\user
host: "remote-host"
  identities: not preserved
 permissions: not preserved
 feature level: unknown
 connectivity: connected

Run a cleartool describe vob:. in the same replica.

Note the replica name.

local-host:M:\def1\dmm>cleartool describe -l vob:.
versioned object base "\dmm"
 created 2007-08-27T16:33:25-04 by userA (userA.user@local-host)
 master replica: original@\dmm
  replica name: original
  VOB family feature level: 5
 VOB storage host:pathname
 VOB storage global pathname "\\local-host\data\clearcase_storage\vobs\dmm.vbs"
 database schema version: 54
 modification by remote privileged user: allowed
 VOB ownership:
   owner WINDOMAIN\userA
   group WINDOMAIN\user
   FeatureLevel = 5

Run the same commands in the destination VOB.

Note the replica names.

Upon as examination of the output of the above commands, it should visible if the replicas may have been misnamed or if the replica specified in the command was incorrect.

Resolving the problem

For Scenario 1:

You need to change the names of any replicas that are incorrect by performing a cleartool rename command from the site that masters the replica object (Replica object that is to be renamed.)

Example: cleartool rename replica:original_name new_name

Review the ClearCase MultiSite Administrators Guide on the topic of Renaming a VOB replica or the ClearCase Command Reference Guide on the topic of rename (cleartool man Renaming a VOB replica) for more information.

For Scenario 2:

Document information

More support for: Rational ClearCase

Software version: 7.0, 7.0.1, 2002.05.00, 2003.06.00

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1289388

Modified date: 02 January 2008