9.6 VOB and View Resynchronization

A VOB database maintains references to one or more view databases, and vice versa. When a VOB or view is restored from backup, the view and VOB are potentially out of sync; some of the references are no longer valid. This skew can cause several problems.

• Elements can become "checked out but removed" when the VOB has recorded that the view has the element checked out, but the view doesn't have a view-private file for the element.

• Elements can become eclipsed by a view-private file when the checkout that was once valid in the view is no longer recognized in the VOB. (The VOB says the element isn't checked out in the view.)

There are a several things you can do to correct the skew and identify and/or eliminate the problems. You can perform the resynchronization described in Resynchronizing Views and VOBs on the restored view immediately following VOB or view restore, or you can wait until problems surface.

Resynchronizing Views and VOBs

To resynchronize views and VOBs, run cleartool ls -recurse -view_only. Look at the output for any checkouts that are marked as checked out but removed.

If the VOB was restored, the user had probably once checked out the version but then either checked it in or canceled the checkout after the VOB was backed up but before it was restored.

• If the version was checked in, the data has been lost.

• If the view was restored, any view-private modifications to the checked-out version have been lost.

In either case, the user must now cancel the checkout (uncheckout) or re-create the version data and check it in.