Special procedures for restoring a PVOB

A PVOB can be restored from backup by using any of the procedures described here. Special procedures must be run after doing so, because restoring a PVOB can introduce skew between the PVOB and its component VOBs. These are the the most common types of skew:

Versions, baselines, stream objects, and label types used by component VOBs might not exist in the PVOB.
Records in the Rational® ClearQuest® database might reference activities that do not exist in the PVOB.

The checkvob command can be used to analyze and, if necessary, fix most types of skew. You can use checkvob to detect skew between the PVOB and its component VOB, and skew between the PVOB and its Rational ClearQuest database. If your PVOB is associated with multiple component VOBs in the project, you must run checkvob for each of these component VOBs.

The commandcheckvob -ucm -vob_onlydetects most types of skew between the restored PVOB and its component VOB. This command checks the PVOB for references it holds to objects in component VOBs. For example, the following command checks a component VOB whose VOB tag is \CVOB:

cleartool checkvob -ucm -vob_only vob:\CVOB

The command checkvob -ucm -crm_dbname detects most types of skew between the restored PVOB and the Rational ClearQuest database. For example, the following command checks for skew in a project named Release-6 in a Rational ClearQuest database named CQ-UCM-DB:

cleartool checkvob -ucm -crm_dbname -project Release-6

For more information about using checkvob to analyze and fix skew between a PVOB and a component VOB, see the checkvob reference page.