checkvob can find and fix problems with storage pools, with hyperlinks, and with global types in an administrative VOB hierarchy. It can also find and fix inconsistencies between PVOBs, components, and an optional ClearQuest database in a UCM environment. For more information, see the Administrator's Guide.
For –fix, you must have one of the following identities:
For –hlink, you must have one of the following identities:
Without –fix (check-only mode), no locks apply. With –fix, the following restrictions apply:
It may be difficult to fix ownership and naming problems with global types if local copies or eclipsing ordinary types are locked.
(Replicated VOBs only) No mastership restrictions.
The following sections describe the options and arguments for storage pool mode, hyperlink mode, global types mode, and UCM mode. For more information about fix-mode processing, see the Administrator's Guide.
Warning: Fixing problems detected with –data can update the VOB irreversibly. If source or DO data containers are missing from the storage pools when checkvob runs, it updates the VOB database, dereferencing these containers with the equivalents of rmver -data (for missing source containers) and rmdo (for missing DO containers).
For details about how checkvob tries to fix the various problems it detects, see the Administrator's Guide.
Note: During check processing, a “healthy” element is one whose containers have the right names, in the right locations, with the right permissions. checkvob does not detect container data corruption.
Note: If pname has the form of an object selector, you must include the –pname option to indicate that pname is a pathname.
For details on how checkvob tries to fix the various problems it detects, see the Administrator's Guide.
pname-in-vob can be the pathname of the VOB tag (whether or not the VOB is mounted) or of any filesystem object within the VOB (if the VOB is mounted). It cannot be the pathname of the VOB storage directory.
Object type | Check/fix behavior |
---|---|
Activity (activity:activity-name[@vob-selector]) | Verifies that activity-name has a valid change set. –fix removes invalid references to versions in component VOBs |
Baseline (baseline:baseline-name[@vob-selector]) | Verifies that baseline-name has valid references to objects in the PVOB. –fix removes invalid references |
Stream (stream:stream-name[@vob-selector]) | Verifies that stream-name has valid references to objects in the PVOB. –fix removes invalid references |
Project (project:project-name[@vob-selector]) | Verifies that references to modifiable components are valid. Verifies that the project references a valid ClearQuest database. Checks all streams, baselines, and activities in the project. –fix removes invalid references |
Folder (folder:folder-name[@vob-selector]) | Checks all projects in the folder and reports problems. To fix, rerun checkvob –ucm –fix and specify the appropriate project, stream, baseline, or activity object. |
Component (component:component-name[@vob-selector]) | Verifies that references to component root directories and component initial baselines held by the PVOB are valid. Reports problems but cannot fix them. |
Project VOB (vob:vob-tag ) | Checks all objects in the PVOB and reports problems. To fix, rerun checkvob –ucm –fix and specify the appropriate project, stream, baseline, or activity object. |
Branch type (brtype:type-name[@vob-selector]) | Checks the specified branch type and all versions on the branch in the specified component VOB. –fix recovers versions to a new activity. |
Label
type (lbtype:type-name[@vob-selector]) | Checks the specified label type in the specified component VOB. –fix re-creates GlobalDefinition hyperlinks as required. |
Component
VOB (vob:vob-tag) | Checks all UCM branch and label types in the specified component and reports problems. To fix, rerun checkvob –ucm –fix and specify the appropriate branch or label type. |
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
cmd-context checkvob /vobs/lib/gui.c
The session's log directory is 'checkvob.11-Apr-98.05:21:17'.
=================================================================
Processing element "/vobs/lib/gui.c@@".
Checking status of 1 referenced containers in pool "s/sdft"...
Initial container status: 0 missing, 0 misprotected.
=================================================================
cmd-context lsvob \vob_lib2
* \vob_lib2 \\saturn\vobstore\vob_lib2.vbs
cmd-context checkvob –pool –source \\saturn\vobstore\vob_lib2.vbs
=================================================================
Starting "source pool" processing at 10-Apr-98.06:35:11
Running from host: saturn
VOB hostname: saturn
VOB host storage pathname: C:\vobstore\lib2.vbs
VOB global storage pathname: \\saturn\vobstore\lib2.vbs
VOB replica oid: 0cdc7b37.f48611cc.b3d5.00:01:80:02:bc:53
VOB host reference time: 10-Apr-98.06:29:59
Processing pools: sdft
Processing of misprotected containers is: ENABLED
Processing of ndata containers is: ENABLED
Processing of unreferenced containers is: ENABLED
Fix processing mode: DISABLED
Poolkind transcript log:
checkvob.20-Apr-98.12.10.40\poolkind_source\transcript
=================================================================
... progress messages ...
=================================================================
Completed "source pool" processing at 10-Apr-98.06:35:37
"source pool" Processing Summary:
Referenced Container Check Processing Time: 00:00:20
*** Referenced Container Fix Processing was not performed.
Unreferenced Container Check Processing Time: 00:00:05
*** Unreferenced Container Fix Processing was not performed.
Installed type managers are OK.
Pool root storage areas are OK.
Pool: s\sdft
Referenced container check processing:
229 containers checked
0 ndata 0 misprotected
22 objects checked
0 ndata 0 misprotected
Unreferenced container check processing:
229 containers checked (47778 kbytes)
0 unreferenced but under age (0 kbytes)
0 unreferenced but maybe needed (0 kbytes)
0 unreferenced containers (0 kbytes, 0 empty)
The VOBs source pools are healthy.
Poolkind transcript log:
checkvob.20-Apr-98.12.10.40\poolkind_source\transcript
=================================================================
cmd-context checkvob –global vob:/vobs/dev
The session's log file is "checkvob.30-Jul-99.17:28:55".
Starting analysis of Admin VOB hierarchy.
Analysis of Admin VOB hierarchy complete.
5 VOBs analyzed, no hierarchy errors found.
Starting "global type" processing.
Detection of eclipsing local copies is: ENABLED
Detection of protection mis-matches is: ENABLED
Detection of eclipsing local locks is: ENABLED
Correction of detected errors is: DISABLED
Completed "global type" processing.
Processed 8 global types in 5 VOBs.
current-dir/checkvob.date-time (default log-pname for –global) |
current-dir/checkvob.date-time/ (default log-dir) |
log-dir/.summary |
log-dir/poolkind_cleartext/transcript |
log-dir/poolkind_derived/transcript |
log-dir/poolkind_source/transcript |
log-dir/summary |
vob-storage-dir/s/sdft/pool_id |
vob-storage-dir/c/cdft/pool_id |
vob-storage-dir/d/ddft/pool_id |
current-dir\checkvob.date-time (default log-pname for –global) |
current-dir\checkvob.date-time\ (default log-dir) |
log-dir\.summary |
log-dir\poolkind_cleartext\transcript |
log-dir\poolkind_derived\transcript |
log-dir\poolkind_source\transcript |
log-dir\summary |
vob-storage-dir\vob_server.conf |
vob-storage-dir\s\sdft\pool_id |
vob-storage-dir\c\cdft\pool_id |
vob-storage-dir\d\ddft\pool_id |
lock, reformatvob, rmdo, rmver, type_manager, vob_restore, vob_snapshot, Administrator's Guide
Copyright© 2003 Rational Software. All Rights Reserved.