regenerate or replacing view storage files

regenerate or replacing view storage files

ClearCase view files in the view storage area can be regenerated or replaced if problems occur with a view. The following files are automatically regenerated when the view is restarted:

· .access_info

· .pid

e) Files that can be regenerated with ClearCase commands:

· .compiled_spec -- regenerate by running cleartool setcs -current

· .hostname -- regenerate by unregistering and re-registering the view

· view.dat -- Snapshot views only: can be regenerated by running the "regen_view_dot_dat.pl" script found in \etc\utils

f) Files that can be manually replaced by making a new view on the same machine as the same user, and copying the affected file(s) to the view storage:

· config_spec

· groups.sd

· identity.sd

· view_db.state (as long as the view is not in the process of being reformatted); db/view_db.dbd (for schema 9 views only; 2002.05.00 and earlier)

· db/view_db_schema_version

· .view - The copy obtained from the new view must be edited to contain the correct information for the old view as described below. The correct information can be obtained from the output of "cleartool lsview -long ".

Line 1: the location of the view storage directory, in hostname:pathname format
Line 2: the view's UUID (unique identifier), which must not be changed
Line 3: the hostname specified in line 1

g) Files that cannot be replaced:

All other files in the db directory except the ones mentioned above ( view_db_schema_version and view_db.dbd)