Re: [cciug] Changing mastership of attribute objects

At the site of the replica to be removed, complete all development work in the replica and use lscheckout or the Find Checkouts tool (available only on Windows) to verify that all checkouts are resolved in the replica to be removed: [axes_VOBtest]

1] cleartool lscheckout -all /vobs/VOBtest at AXES Replica Site.

(no output means no checkouts)

Transfer mastership of all objects to another replica.   [ To YOUR_REPLICA]

At the site of the replica to be removed AXES [ axes_VOBtest] , transfer mastership of all objects mastered by the AXES replica to another replica [YOUR_REPLICA]. If the replica to be removed is not self-mastering, transfer mastership to the replica's master replica.

2] multitool chmaster -all -long YOUR_REPLICA       [ Execute at  AXES Replica ]

Changed mastership of versioned object base ...

...

Changed mastership of all objects

The replica that receives the mastership can later transfer mastership to other replicas.

Export and send an update packet from the replica to be removed.

The replica to be removed must send its final changes, including checkins and mastership changes, to the replica receiving mastership. The replica to be removed can broadcast its final changes to all other replicas, but it must update its master replica.

3] multitool syncreplica -export -fship YOUR_REPLICA

Import the update packet at the replica that is (or will become) the master of the replica to be removed.

4] multitool syncreplica -import -receive

At the master replica, remove the replica object of the replica to be removed.

5] multitool rmreplica axes_VOBtest@/vobs/tromba

At the master replica, export and send an update packet to the remaining replicas in the VOB family.

This update packet notifies the other replicas of the replica removal.

6] multitool syncreplica -export -fship <replica names>

Hope this heps

Santosh Angadi