Troubleshooting
Problem
This technote explains why the IBM Rational ClearCase logs identify database error, db_VISTA database error -912, and provides instructions to troubleshoot the problem.
Symptom
The following errors may be seen in the vobrpc_server_log:
04/26/00 11:20:20 vobrpc_server(16502): Ok: Rollforward recovery using "/usr/vobstore/myvob.vbs/db/vista.tjf" started Wed Apr 26 11:20:20 2000
04/26/00 11:20:20 vobrpc_server(16502): Ok:
04/26/00 11:20:20 vobrpc_server(16502): Ok: *** db_VISTA database error -912 - error seeking in database file
04/26/00 11:20:20 vobrpc_server(16502): Ok: Rollforward recovery using "/usr/vobstore/myvob.vbs/db/vista.tjf" failed Wed Apr 26 11:20:20 2000
04/26/00 11:20:20 vobrpc_server(16502): Ok: : status -912
04/26/00 11:20:20 vobrpc_server(16502): Error: DBMS error in /usr/vobstore/myvob.vbs/db.
04/26/00 11:20:20 vobrpc_server(16502): Error: db_VISTA error -912 (errno == "Invalid argument")
04/26/00 11:20:20 vobrpc_server(16502): Error: Cannot open database in "/usr/vobstore/myvob.vbs/db"
04/26/00 11:20:20 vobrpc_server(16502): Error: Error from VOB database: "/vobs/myvob".
04/26/00 11:20:20 vobrpc_server(16502): Error: Trouble opening VOB database: "/vobs/myvob".
The db_server_log also contains the following errors:
04/26/00 11:20:20 db_server(16383): Ok: Rollforward recovery using "/usr/vobstore/myvob.vbs/db/vista.tjf" started Wed Apr 26 11:20:20 2000
04/26/00 11:20:20 db_server(16383): Ok:
04/26/00 11:20:20 db_server(16383): Ok: *** db_VISTA database error -912 - error seeking in database file
The view_log also contains the following errors:
04/26/00 11:20:20 view_server(16314): Error: Unexpected error in VOB "myhost:/usr/vobstore/myvob.vbs" op vob_ob_get_gen_num:error detected by ClearCase subsystem
See vobrpc_server_log on host myhost
04/26/00 11:20:20 view_server(16314): Warning: Unable to open vob 'myhost:/usr/vobstore/myvob.vbs': unknown error in VOB
Cause
This error can relate to one or more of the following problems:
- Disk Space
- Confused Processes
- Database Limitations
- Database Corruption
Resolving The Problem
DISK SPACE
Check for inadequate disk space on the VOB server. If the file system is low on disk space, move the VOB storage to a file system with more disk space.
CONFUSED PROCESSES
Unmount the VOB and kill any lingering vob_server processes using the albd_list utility.
Note: Review technote 1148639 for more details on albd_list and its usage.
DATABASE LIMITATIONS:
Check the size of the string file (vob_db.str_file) and transaction files (vista.tjf, vista.taf, vista.tcf) in the VOB storage db directory. These files may have reached their maximum size limitation of 2 gigabytes.
String File: Review technote 1122951 for more information on reducing the size of the string file.
Transaction Files: Follow the steps outlined in technote 1133944 to resolve the problem.
Note: If the transaction files (vista.*) sizes are under 2 gigabytes, it is possible that the transaction files have become corrupted. Follow the same instructions above to resolve the problem.
If this error occurs when attempting to remove the next-to-last MultiSite replica in a replicated VOB family, the transaction journaling file limit may have been exceeded. Refer to technote 1128018 Unable to remove the last replica of the family for information about a resolution.
DATABASE CORRUPTION:
Run the dbcheck utility to see if there is any database problems and report any problems to ClearCase technical support.
Note: Review technote 1122748 for instruction on how to run the dbcheck utility.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21123349