Finds and fixes inconsistencies between VOB database and storage pools, problems with hyperlinks, and problems with global types
Product | Command Type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
Platform |
---|
UNIX |
Windows |
Check/fix storage pools
Check/fix hyperlinks
Check/fix global types
checkvob can find and fix problems with storage pools, with hyperlinks, and with global types in an admin VOB hierarchy. For more information, see the Administrator's Guide.
For -fix, you must have one of the following identities:
VOB owner
root (UNIX)
Member of the ClearCase group (ClearCase on Windows)
Local administrator of the ClearCase LT server host (ClearCase LT on Windows)
For -hlink, you must have one of the following identities:
Object owner
Object group member
VOB owner
root (UNIX)
Member of the ClearCase group (ClearCase on Windows)
Local administrator of the ClearCase LT server host (ClearCase LT on Windows)
Locks: Without -fix (check-only mode), no locks apply. With -fix, the following restrictions apply:
The VOB must be unlocked (or locked with lock -nusers user-running-checkvob).
Problems cannot be fixed if the affected element or pool is locked. Use -ignore to modify this behavior.
It may be difficult to fix ownership and naming problems with global types if local copies or eclipsing ordinary types are locked.
Mastership: (Replicated VOBs only) No mastership restrictions.
The following sections describe the options and arguments for storage pool mode, hyperlink mode, and global types mode. For more details on fix-mode processing, see the Administrator's Guide.
SPECIFYING A VIEW. Default: Uses the current view context. If you attempt to run checkvob without a view context, you are prompted to continue. Without a view context, checkvob cannot generate VOB pathnames in problem object reports, so it reports OIDs instead of pathnames. In general, run checkvob from a view.
LOG FILE DIRECTORY. Default: checkvob creates in the current directory a log file directory named checkvob.date-time. With -pool, several log files are created, including a summary file and one file per pool analyzed. Otherwise, a single transcript file stores a report on each individual file examined.
FIX MODE. Default: Reports any problems, but does not try to fix them.
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).
DATABASE/POOL INCONSISTENCIES. Default: Scans pools or individual file containers looking for all detectable problems.
SETUP MODE. Default: None. Specify -setup to run checkvob in setup mode.
POOL MODE. Default: None. Specify -pool and a vob-stg-pname argument in order to process one or more storage pools.
INDIVIDUAL FILE MODE. Default: None. If you do not use the -pool option, you must specify one or more file-pname arguments.
HYPERLINK MODE. Default: None. Use -hlinks to run checkvob in hyperlink mode. checkvob prompts for confirmation before deleting each partially unavailable hyperlink it detects.
type-name | Name of the hyperlink type | |
vob-selector | Object-selector for a VOB, in the form [vob:]pname-in-vob. The pname-in-vob can be the pathname of the VOB-tag (whether or not the VOB is mounted) or of any file-system object within the VOB (if the VOB is mounted). |
pname | ||
NOTE: If pname has the form of an object selector, you must include the -pname option to indicate that pname is a pathname. | ||
vob-selector | vob:pname-in-vob | |
pname-in-vob can be the pathname of the VOB-tag (whether or not the VOB is mounted) or of any file-system object within the VOB (if the VOB is mounted). It cannot be the pathname of the VOB storage directory. | ||
attribute-type-selector | attype:type-name[@vob-selector] | |
branch-type-selector | brtype:type-name[@vob-selector] | |
element-type-selector | eltype:type-name[@vob-selector] | |
hyperlink-type-selector | hltype:type-name[@vob-selector] | |
label-type-selector | lbtype:type-name[@vob-selector] | |
trigger-type-selector | trtype:type-name[@vob-selector] | |
pool-selector | pool:pool-name[@vob-selector] | |
oid-obj-selector | oid:object-oid[@vob-selector] | |
The following object selector is valid only if you use MultiSite: | ||
replica-selector | replica:replica-name[@vob-selector] |
GLOBAL TYPES MODE. Default: None. You must specify -global.
LOG FILE. Default: checkvob creates in the current directory a file named checkvob.date.time.
FIX MODE. Default: Reports any problems, but does not try to fix them.
attribute-type-selector | attype:type-name[@vob-selector] | |
branch-type-selector | brtype:type-name[@vob-selector] | |
element-type-selector | eltype:type-name[@vob-selector] | |
hyperlink-type-selector | hltype:type-name[@vob-selector] | |
label-type-selector | lbtype:type-name[@vob-selector] |
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. In Attache, cmd-context represents the workspace 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.
Check a single element's data container.
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.
=================================================================
Perform a routine check on a small, healthy VOB's source pools.
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
=================================================================
Check all global types in the admin VOB hierarchy containing the VOB /vobs/dev.
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
reformatvob, rmdo, rmver, type_manager, vob_restore, vob_snapshot, Administrator's Guide
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |