rgy_getuuid_by_uuid failed errors in clearcase

Posted on May 9, 2008

Problem
This technote discusses the symptoms of and solutions for the error rgy_getuuid_by_uuid as it relates to IBM® Rational® ClearCase® VOBs and views.
Cause
At times the following entries may be seen in the ClearCase logs:10/18/99 11:55:37 view_server(13967): Error: Operation "rgy_getuuid_by_uuid" failed
("23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92"): ClearCase object not found.
10/18/99 15:22:48 view_server(13967): Error: Operation "rgy_getuuid_by_uuid" failed
("23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92"): ClearCase object not found.
The rgy_getuuid_by_uuid error indicates that ClearCase is trying to look something up in the ClearCase registry by its UUID and is failing, finding no entry with that UUID.

This type of error could originate from either a view or a VOB since both use a UUID identification object. The errors above correspond from a view_server process and therefore relate to a view. If the errors correspond to a VOB, it is likely that the output would look similar to the following:

cleartool: Error: Unable to find replica in registry for VOB with object ID:"9250ab61.6f04465d.b3f4.d7:a4:a1:74:0c:85"
cleartool: Error: Unable to locate versioned object base with object id: "9250ab61.6f04465d.b3f4.d7:a4:a1:74:0c:85".
In this case, the error is likely the result of some confusion with the VOB hyperlink to an AdminVOB.
Review the IBM Rational ClearCase Administrator’s Guide for more information about AdminVOBs.
Solution
If the errors originate from the view_server and or log, check to see if the error is reporting on the same UUID. If so there is probably one view that has been improperly deleted but still has checkouts in some of the VOBs.It is also good to note that such an error, specifically in the view_log of the view server host machine, but not the vob_log of the VOB server host machine, can be indicative of a client having a mounted VOB that has since been removed (from the registry and its storage). This causes the client system to continue to try and access the now removed VOB, resulting in rgy_getuuid_by_uuid errors. The resolution to this problem is to simply issue a cleartool umount <vob tag> of the removed VOB on the problem client system.

Run the rmview -uuid command to remove all references to this view in all VOBs on the server (review to technote 1122515 for more details):

%> cleartool rmview -avobs -uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92
Removed references to view "23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92" from VOB "/vobs/admin".
Removed references to view "23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92" from VOB "/vobs/local".
Removed references to view "23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92" from VOB "/vobs/pvob".
If the errors in the logs report multiple UUIDs, then check all of the VOBs to see if there are multiple deleted views. Look for the views listed in the “VOB holds objects from the following views” section in the output of the describe -long vob:<vob> command:

% > cleartool describe -long vob:/vobs/grouptest
versioned object base "/vobs/grouptest"
created 27-Jun-02.05:27:40 by John Doe (jdoe.grouptest2@host1)
VOB family feature level: 2
VOB storage host:pathname "host1:/vobstore/grouptest.vbs"
VOB storage global pathname "/net/host1/vobstore/grouptest.vbs"
database schema version: 54
VOB ownership:
owner jdoe
group grouptest2
Additional groups:
group sybase
group grouptest1
VOB holds objects from the following views:
anemone:/my/storage/mollyview.vws [uuid d79fd5ce.e83911d5.b275.00:01:80:f0:f4:92]
anemone:/my/storage/timb.vws [uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92]
Attributes:
FeatureLevel = 2
Hyperlinks:
AdminVOB@53@/vobs/grouptest -> vob:/vobs/admin
It is likely that there will be references to these views in the VOBs.
Before removing each view, ensure that it is not currently registered by running the cleartool lsvob and lsview commands:

% > cleartool lsview -uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92
cleartool: Error: No matching entries found for uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92.

% > cleartool lsvob -uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92
cleartool: Error: No matching entries found for uuid 23dd562d.8ebf11d6.a7d9.00:01:80:f0:f4:92.

Note: Similar errors may be seen if a view or VOB was created in a different region. Be sure to run lsview or lsvob in all the regions using the -region option for each region in your environment.

If the UUID displays an entry in either registry table, then do not remove it.
Instead, run the rgy_check -views or rgy_check -vobs command depending on which registry table it turned up in and then repair the problems it reports.


Note: If it is not possible to identify where the original view was located (perhaps it was created on one of many client machines not identified in any error message even running lsvob -long), then the only option is to wait until someone states that one of their views is not working. This issue can then be investigated properly. Meanwhile the error message in the vob_server logs will not cause any harm and can be ignored.

Popularity: 4% [?]

Related Posts:

» Filed Under Other

Comments

Leave a Reply