About checkvob

VOBs have complex internal and external relationships that can sometimes be disrupted by system or network failures or when a VOB is restored from backup. checkvob is a cleartool subcommand that can find, and in many cases fix, a variety of problems in these relationships.

checkvob can find and often fix these problems:

Inconsistencies between a VOB’s database and its pools
Improper protections on storage pools
Improperly configured AdminVOB hyperlinks
Local types that eclipse global types
Broken cross-VOB hyperlinks, including those that link UCM components to PVOBs.

You can use checkvob for a variety of purposes:

When you restore a VOB from backup media without using vob_restore (the vob_restore script runs checkvob as part of its normal operation)
When you restore a Rational® ClearQuest® database used by a UCM project
When you move a VOB
As part of your periodic VOB maintenance routine

Replicated VOB considerations
Using checkvob to find and fix internal VOB inconsistencies
A VOB storage directory contains a VOB database and a number of storage pools. Any operation that modifies VOB data makes changes to the database and at least one pool. When inconsistencies arise between the contents of a VOB database and the contents of its pools, VOB data integrity may be damaged.
Using checkvob to find and fix problems with global types
checkvob can find and often fix many problems that occur in an administrative VOB hierarchy.
Using checkvob to find and fix broken hyperlinks
Careful use of checkvob –hlinks can find and allow you to fix problems with administrative VOB hierarchies.
Using checkvob in a UCM environment
checkvob has a special set of capabilities enabled by the –ucm option that can detect and correct many of the problems that may arise when one or more members of a related set of databases are restored from backup or are otherwise affected by a system or network failure.

Parent topic: Periodic maintenance