About rgy_getuuid_by_uuid failed errors

Resolving The Problem

Possible solutions to this error message include:

1. Server error messages:
   
• Client Mounted VOB no longer present: Attempt to unmount the VOB. Failing that, it may be necessary to restart ClearCase on, or reboot, the client host. The steps in the diagnosis section above should help provide information regarding the identity of the client host.
  
• Client-Mounted VOB not visible to view server: Generally, this occurs because the view server is in a different registry region than the client. To resolve this, create a VOB tag for the "invisible" VOB. If the view server uses a different registry server, it will also be necessary to register the VOB. The steps are:
  
1. Collect the VOB information on the client using "cleartool lsvob -long ..."
   
2. Verify that the view server can see a VOB object entry for the vob by running cleartool lsvob -uuid {replica uuid from #1} -region *"
   
3. create a tag for the VOB using the cleartool mktag command. For example:
   cleartool mktag -vob -tag \mkvobtest -host ccsvr -hpath c:\ccstg\vobs\mkvobtest.vbs -gpath \\ccsvr\ccstg\vobs\mkvobtest.vbs \\ccsvr\ccstg\vobs\mkvobtest.vbs
   
• Client-mounted VOB not accessible to the view server. This would require separately diagnosing the cause of this inaccessibility and resolving that issue.
  
  
2. Client issues:
• Replica not found or similar errors:
  
• VOB not registered in client region: This is the mirror image of the above "not visible to view server" condition, and the issue is resolved by tagging the missing VOB on in the client's region.
  
• VOB not replicated to the client's site. This issue would be resolved by creating a new replica at the client site.
  
• VOB deleted. Generally speaking, this would occur if cleartool rmvob was not used to remove the VOB as that command will delete all cross-VOB hyperlinks that refer to the removed VOB. The simplest way to resolve this would be to restore the VOB from backup. There may be complications if the VOB in question was replicated or was a UCM VOB. In those cases, contact IBM Rational Client Support for further assistance.
  
  
• View not present or not responding. Generally speaking, a view does not have to be tagged in a client's region to be accessed for Derived Object promotion or winkin as long as it is tagged in the view server's region. So in many cases the cause of this issue is that the view in question is no longer present.
  
• View removed. If the view was removed or is inaccessible, references to the view have to be removed with the cleartool rmview -uuid command. This command will remove all references to a given view in all mounted VOBs (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".
  
  
• View corrupt or otherwise inaccessible. In this case, the view would have to be removed manually removing the tag; removing the view object entry; removing or renaming the view storage directory if necessary; and finally running the rmview -uuid -all command.
  
  For example:
  >cleartool endview -server mkview-test
  >cleartool rmtag -view mkview-test
  >cleartool unregister -view c:\ccstg\views\mkview-test.vws
  >rmdir /s /q c:\ccstg\views\mkview-test.vws
  >cleartool rmview -uuid 394dcea6.1bd246e1.9601.df:5d:70:12:89:86 -all
  Removed references to view "ccsvr:\\ccsvr\ccstg\views\mkview-test.vws" from VOB "ccsvr:C:\ccstg\vobs\vob1.vbs".
  Removed references to view "ccsvr:\\ccsvr\ccstg\views\mkview-test.vws" from VOB "ccsvr:c:\ccstg\vobs\mkvobtest.vbs".                                                                                                                                        Removed references to view "394dcea6.1bd246e1.9601.df:5d:70:12:89:86" from VOB "ccsvr:c:\ccstg\vobs\ucmpvob.vbs".
  
  
• View moved to another server or storage location. This issue can be resolved by updating the view location in the vob. To perform the update:
  
1. Start the view
2. CD through the view into any directory in the VOB
3. Check out any object, and then undo the checkout. The view location will be updated in the VOB.
   Note that a describe on the VOB may not immediately show this on hosts that have that information cached.

Notes:

• 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:
  
  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.
  
  Review the IBM Rational ClearCase Information Center on the topic of rgy_check (cleartool man rgy_check) for more information.
  
  
• 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.