recoverview

When necessary, recoverview is invoked by a dynamic view's associated view_server process. Enter this command yourself if messages in the view log (view_log) suggest view database corruption (for example, INTERNAL VIEW DB ERROR).

recoverview uses reformatview; that is, recovery involves a dump/load of the view database. recoverview deletes the old, invalid view database, which reformatview has renamed to db.dumped.

Depending on the state of the view database, this process may cause certain information to be lost. After a view is recovered, consult the view log to investigate possible data loss.

For more information, see the reformatview reference page.

A file in view-private storage (including the view-private contents of a checked-out version) is normally accessed through a VOB pathname. That is, the file appears to be located in the VOB, but is actually stored in the view. But this view-VOB correspondence can be disrupted:

• A VOB can become temporarily unavailable, for example, by being unmounted.
• A VOB can become permanently unavailable, by being deleted.
• A particular VOB directory can become unavailable permanently, by being deleted with an rmelem command.

In all these cases, view-private files that are accessed through the unavailable VOB structure become stranded; the files cannot be used for normal VersionVault operations, because there are no VOB pathnames through which they can be accessed. You can resynchronize your view with the available VOBs with the –vob and –dir options. This recovers stranded files by moving them into the view's lost+found directory. Recovered files remain inaccessible to normal VersionVault operations; you can access them through the view storage directory, using standard operating system utilities and commands.

The following option synchronizes the dynamic view with one or more VOBs. With this option, recoverview moves all stranded files to the lost+found subdirectory. A typical time to synchronize is after performing a relocate operation.

–syn/chronize [ –vob pname-in-vob ]

Synchronizes the view with all VOBs in which the view has created view-private files. With –vob, synchronizes the view only with the VOB specified by pname-in-vob.

Default

recoverview displays a Recovery not needed warning message and exits immediately if the view database does not need to be recovered.

–f/orce

Performs a view database recovery, whether or not it is necessary. Suppresses the warning message in the situation described above.

Default

None.

–tag view-tag

The view tag of any registered dynamic view.

view-storage-dir-pname

The pathname of a dynamic view storage directory. Use the lsview command to list a view's storage directory.

Important: Make sure that the current working directory is not the same as, or anywhere below view-storage-dir-pname.

The following options take internal VersionVault identifiers for a VOB or a VOB directory (vob-identifier and dir-identifier) as arguments. The lsprivate command uses these identifiers when listing an inaccessible VOB or VOB directory.

–vob vob-identifier

Moves all view-private files that correspond to the specified VOB to the lost+found directory.

–dir dir-identifier

Moves all view-private files that correspond to the specified directory element to the lost+found directory.