IBM Support

Rebase error "unable to find replica in registry"

Troubleshooting


Problem

IBM Rational ClearCase Unified Change Management (UCM) Rebase -complete reports an error "unable to find replica in registry" yet completes successfully if any non-replicated stream is using the baseline as a foundation.

Symptom

In a ClearCase MultiSite UCM environment with multiple project VOBs (PVOBs), and working at a site that does not have a replica of all project VOBs, if you rebase a stream onto a baseline that is also being used as Foundation for a stream in a project VOB that does not have a local copy, completing a rebase will report the following error messages:

cleartool: Error: Unable to find replica in registry for VOB with object ID:"5265d8ab.7dd911dd.962b.00:01:84:aa:d3:54"
cleartool: Error: Unable to locate versioned object base with object id: "5265d8ab.7dd911dd.962b.00:01:84:aa:d3:54".

Cause

Although the rebase does complete successfully, the message correctly indicates that there is a reference to a PVOB that has not been replicated to the site performing the rebase operation. During the rebase we need to traverse any dependencies and when we find a hyperlink which exists to a PVOB which is not available (in this case it is not replicated to the local site), we report an error.

Diagnosing The Problem

Steps to reproduce this behavior:

1. Create two PVOBs at site A and replicate only one PVOB.
2. Create a project in the replicated PVOB, replicate and have a user join a project at site B.
3. Create a new baseline in the project and recommend it.
4. Create a read only project in PVOB2 using the new recommended baseline from the project.
5. Replicate the PVOB and component VOB.
6. Rebase -recommended the user stream at site B.
7. The error message occurs on rebase -complete, but the rebase is successful.

Resolving The Problem

You can safely ignore the message as this does not cause the rebase to fail.
This message will not occur if the PVOB is replicated to the site performing the rebase.

You can identify which PVOB is causing the error by listing the VOBs in each replica and verifying which PVOB is not replicated.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Synchronization","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.1.2;7.1.1.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"UCM: Rebase","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21614234