Error Reading Vob Objects
Contents |
ClearCase object not found; malformed or missing replica_uuid file; Unable to get VOB tag registry information for replica uuid; malformed; replica uuid; replica_uuid; 1228175 Technote cleartool error is not a registered vob tag (troubleshooting) Problem(Abstract) This technote outlines the possible causes for the error ClearCase Object
Clearcase Remove View
Not Found when attempting to mount an IBM Rational ClearCase VOB on Microsoft Windows, Linux or UNIX. Cause Attempts to mount a VOB results in the following error: ClearCase Object Not Found This error may get reported in the VOBRPC error log: 01/06/2006 09:24:34 vobrpc_server(5016): Error: vobrpc_server.exe(5016): Error: Unable to get VOB tag registry information for replica uuid "db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea": ClearCase object not found This error may get reported in the vob_scrubber log: vob_scrubber: Error: Unable to get VOB tag registry information for replica uuid "db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea": ClearCase object not found Note: All of the above errors may not occur when the ClearCase Object Not Found error occurs. These are just possible indicators of the below detailed causes to help with identifying the problem. This error will occur when trying to mount the VOB before the VOB tag creation is complete. This would be due to a timing issue where the cleartool mkvob and cleartool mount operations are done via a script, and maybe a longer pause is required before the VOB is mounted on a remote host. This would also be true in an environment where the VOB creation takes several moments to complete, and there is an extended period before the VOB tag is available for users to mount. Note: This does not occur as a result of the cleartool mount that is executed automatically during the cleartool mkvob operation. Cause 2 The VOB tag may still exist even though the VOB storage (or VOB server host) are no longer available in the ClearCase network. This will happen as a result of improper removal of the VOB storage. Cause 3 The server storage location (network share or export) is not available. When mounting a VOB, the location that the VOB is stored must be accessible from the host that you are trying to mount the VOB. Cause 4 If the VOB is not
"timed out trying to communicate with ClearCase remote server. " RPC:timed out; UDP; buffer; RATLC01340611; timed out trying to communicate with ClearCase remote server Technote (troubleshooting) Problem(Abstract) This technote describes some symptoms that will occur when the workload on an IBM Rational ClearCase UNIX server exceeds the capacity of the server, and some measures that can be taken to relieve them. Symptom Intermittently, http://www.ibm.com/support/docview.wss?uid=swg21228175 and particularly during peak usage periods of the day, users of both ClearCase Remote Client (CCRC) and full ClearCase client (ClearCase Explorer, for example) experience "hangs" which usually will eventually end with a pop-up message "timed out trying to communicate with ClearCase remote server". Checking the ClearCase logs on the server shows http://www.ibm.com/support/docview.wss?uid=swg21577649 messages like the following examples: >cleartool getlog -around now 10 albd db vobrpc ccfs ============================================================================= Log Name: albd Hostname: vobhost Date: 2011-10-09T10:23:16+08:00 Selection: Lines between 2011-10-09T10:08:16+08:00 and 2011-10-09T10:38:16+08:00 displayed ----------------------------------------------------------------------------- 2011-10-09T10:18:04+08 albd_server(1319118): Error: Server vobrpc_server (pid=2809890) on "/vob_store/VOBs/aaa.vbs" died on startup; marking it as "down". ============================================================================= Log Name: db Hostname: vobhost Date: 2011-10-09T10:23:16+08:00 Selection: Lines between 2011-10-09T10:08:16+08:00 and 2011-10-09T10:38:16+08:00 displayed ----------------------------------------------------------------------------- 2011-10-09T10:11:35+08 db_server(880886): Error: albd_rgy_findbyuuid_entry call failed: RPC: Timed out 2011-10-09T10:11:35+08 db_server(880886): Error: Trouble contacting registry on host "vobhost": timed out trying to communicate with ClearCase remote server. 2011-10-09T10:11:35+08 db_server(880886): Error: Error searching for replica e49551ac.d21b11dc.a041.00:02:c3:0d:60:4c in registry: error detected by ClearCase subsystem 2011-10-09T10:11:46+08 db_server(1642540): Error: albd_server_idle call failed: RPC: Timed out 2011-10-09T10:11:46+08 db_server(1642540): Error: Error sending idle message to albd server: timed out trying to communicate with ClearCase remote server
available; Unable to find replica in registry; Unable to locate versioned object base with object id; Unable to http://www.ibm.com/support/docview.wss?uid=swg21231183 search for process guards; Unable to determine administrative VOBs of VOB; Error http://www.samecs.com/how_do_i/ClearCase_VOBs/ClearCase%20VOBs%20how%20do%20I.htm detected by process execution manager; Process execution failure; Trouble finding the global definition for local type; adminvob; mkhlink; rmhlink; checkvob; admin vob; 1231183 Technote (troubleshooting) Problem(Abstract) Errors such as "Unable to find replica in registry" or "Unable to determine administrative VOBs" or "Trouble finding the error reading global definition" occur when an IBM Rational ClearCase VOB hyperlink between an AdminVOB and its client VOB is broken. Symptom SCENARIO: An AdminVOB has been deleted by mistake. The deletion of the VOB was not performed using the ClearCase command cleartool rmvob or all the VOBs were not available at the time of deletion. After the error reading vob VOB has been removed lots of different operations related to metadata fail with a cryptic error messages such as:
cleartool: Error: Unable to find replica in registry for VOB with object D:"d3fbde9c.c78e4816.aa15.c6:47:7a:2a:94:37"
cleartool: Error: Unable to locate versioned object base with object id: "d3fbde9c.c78e4816.aa15.c6:47:7a:2a:94:37".
cleartool: Error: Unable to search for process guards
cleartool: Error: Unable to unlock versioned object base "
Making new metadata (such as a label or a branch) results in the following errors:
% cleartool mklbtype -ordinary XX
cleartool: Error: Unable to find replica in registry for VOB with object ID:"d010b75e.4d1311d0.a11c.00:01:80:82:10:c2"
cleartool: Error: Unable to locate versioned object base with object id: "d010b75e.4d1311d0.a11c.00:01:80:82:10:c2".
cleartool: Error: Unable to determine administrative VOBs of VOB "\sys".
cleartool: Error: Error detected by process execution manager
cleartool: Error: Process execution failure - aborting...
cleartool: Error: Unable to create label type "XX".
M:\akemim_view\ch>cleartool mkbrtype -ordinary XX Comments for "XX": . cleartool: Error: Unable to
updated 12-Nov-09) · Elements – identifying by oid, source container, etc... · Triggers – copying, ACL’s, applying, etc... · Types & Type manager – manually reconstruct cleartext, magic files, type manger, restoring elements, etc... · Links - hard links, etc... · VOB (Raima) database – Raima database errors. · VOB database – 2GB database files limit, reducing the size of string file, etc... · Storage - .(dot) identify file, renaming VOB storage, VOB tags, etc... · Backup & restore – about file system snapshots, etc... · ClearCase commands – rmname and checkouts, etc... · Scripts & utilities – changing ownership of all objects in, listing locked, last time VOB accessed, etc... · Limitations – of storage, etc... · Problems & Issues – VOB symbolic link issue, etc... · Addendums – to: mkvob –nremote_admin, etc Table of Contents ClearCase VOBs - “How do I” covers: (Last updated 12-Nov-09) 1 Table of Contents. 1 Elements. 5 1. How do I – understand using directory protections is not sufficient to protect the contained elements. 5 2. How do I - determine the full pathname and version of an element identified only by its oid. 5 3. How do I - Identify elements by the source container path. 6 4. How do I – understand the Primary Group requirements for element creation. 8 5. How do I - Restore an element that has been rmnamed. 9 6. How do I – understand what the History Mode element means. 11 7. How do I - List and count the number of elements in VOB. 11 8. How do I – understand the “db_obj_delete_V3: RPC: Unable to receive; errno = Connection reset by peer when running rmelem” issue 13 Triggers. 13 9. How do I - determine the amount of elapsed time ClearCase spends in trigger logic. 13 10. How do I - create a preop checkin trigger that does not fire on directories. 1