Restoring a component VOB

When you restore from backup a component VOB from a UCM project, the following types of skew may be introduced:

Change sets and baselines defined in the PVOB might reference versions and perhaps elements that do not exist in the component (because they were created after the component VOB was backed up).
If the VOB contains multiple components, components that were created after the most recent backup are referenced in the PVOB but do not exist in the component VOB.

To analyze and, if necessary, fix these types of skew, use cleartool checkvob –ucm:

Restore the component VOB.
Establish a working view. This step is recommended, but not essential. If you run checkvob –ucm in a view, you do not have to specify the PVOB on the command-line, and checkvob can report names of elements that have problems and have a version that is selected by the view. (Versions that have problems but are not selected by the view are reported by numerical ID).
In the view, go to the root directory of the PVOB.
Run checkvob –ucm to detect skew between the PVOB and the restored component. The following command checks a component named lib in a VOB whose VOB tag is \CVOB:
cleartool checkvob –ucm –component:lib@\CVOB

Note: If a component VOB contains more than one component, all components in the VOB are checked when you use checkvob –ucm –component.