Question & Answer
Question
Which IBM Rational ClearCase VOB database files can be regenerated or replaced if a problem occurs?
Cause
If you are receiving errors indicating that one of the files in the db directory does not exist or is missing, it is a good idea to manually inspect the database directory to make sure the directory tree is intact.
Answer
There are several possible problems that can cause errors indicating database files are missing when they are in fact not missing.
A database directory should contain the following 13 files:
vista.taf
vista.tcf
vista.tjf
vob_db.d01
vob_db.d02
vob_db.d03
vob_db.dbd
vob_db.k01
vob_db.k02
vob_db.k03
vob_db.k04
vob_db.str_file
vob_db_schema_version
A brief definition of the types of files are listed below:
VISTA FILES (vista.taf, vista.tcf, vista.tjf)
These are known as journal files and can be automatically regenerated if missing.
Manually regenerate these files ONLY through Support instruction.
Instructions:
1. Lock the VOB (if possible)
2. Stop ClearCase processes on the server
3. Delete the vista.* files on the file system
4. Start ClearCase
5. Unlock the VOB (if locked).
Note: If one file is removed (or missing) the other files should also be removed during this procedure to maintain consistency.
DATABASE FILES: vob_db.d01, vob_db.d02, vob_db.d03
These are the data files for the VOB. If missing or corrupted, they cannot be replaced or regenerated. The VOB must be restored from backup (or the replica re-created, in the case of MultiSite).
Note: A single database file should not be restored from backup. Doing so may result in an inconsistent database and thus corrupt the entire repository.
DATABASE FILE: vob_db.dbd
This is another database file; however, if lost or corrupted can be replaced. Review technote 1135766 on how to replace this file.
KEY FILES: vob_db.k01, vob_db.k02, vob_db.k03, vob_db.k04
These are key files, and if lost or corrupted (in most cases) can be regenerated by performing a keybuild. Contact IBM Rational Client Support for assistance with running keybuild.
Note: Do not perform a keybuild without the express instruction from Rational Support. Improper use of keybuild can cause irreparable damage to the VOB database.
STRING FILE: vob_db.str_file
This file contains string data for comments (that exceed 64 characters) and Configuration Records (CR's) for Clearmake created Derived Objects (DO's). This file cannot be regenerated. The size of the file can be reduced. Follow the steps outlined in technote 1122951 to learn how to reduce the size of this file.
SCHEMA VERSION FILE: vob_db_schema_version
This is a text file that contains the schema version for the VOB database, and should contain either "54" or "80". This file can be replaced if missing. It can either copied from another VOB storage location with the same schema or manually recreated and modified with a text editor to include the schema version of the VOB.
Review the ClearCase Administrators Guide on the topic of VOB database for more information.
ADDITIONAL INFORMATION
LOGS DIRECTORY: (logs)
This directory is used by the Vista files as a temporary spot for their processing. It is not unusual to find that this directory is empty, as the temporary spot is usually cleaned up afterwards. Any files here should not normally need to be touched by a ClearCase administrator unless otherwise directed by Rational Client Support to do so and ONLY if the VOB has been locked first and the journal (vista) files have been processed.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21207386