Kbase 16614: dbrpr: **ERROR - Truncate your bi or use -F Option
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
SYMPTOM(s):
proutil dbname -C dbrpr fails to start with Truncate your bi or use -F option
Using dbrpr utility
**ERROR - Truncate your bi or use -F Option
dbrpr: what to do when the .bi file won't truncate
CAUSE:
There are times when, due to corruption, the bi file cannot be truncated. Truncating the .bi is necessary in order to perform a database repair. If the bi file is not truncated a message is displayed indicating you need to, or to use the -F option.
FIX:
DBRPR is a non-documented, non-supported utility. This utility is provided to assist Progress Technical Support staff in assisting customers when diagnosing or dealing with corruption issues. Caution should be exercised when using this option to proutil.
It is possible to use the -F option to force access into the dbrpr utility. This is the same as forcing into a database. The database is marked as damaged and will cause logical corruption and possible structural corruption to this database.
Upon entering the dbrpr menu a message may be displayed which states:
"warning totblks is too low, fix it (yes
o)." Totblks is the total number of database blocks in the database and is maintained in the master block. When you receive this error it is indicative of the actual amount of blocks in the database, not being consistent with this entry in the master block of the database. If this is the case, selecting "yes" will fix the inconsistencies between these two values in the master block.
If you did not receive the warning about totblks and still cannot access the database, then this is an indicator of possible bi corruption. Recommended recovery - go to backup.
Command for accessing dbrpr with the force option and redirecting output to a file is: proutil dbname -C dbrpr -F -G 0 | tee dbrpr.out (sends output to file and stdout)
DEFINITIONS:
============
Logical - No crash recovery is performed. Crash recovery is a cornerstone of how Progress maintains Data Integrity. No transactions will be undone and the last 2 clusters worth of transactions will not be redone.
Structural - Corrupt schema, records or blocks within the database. DBRPR allows you to scan blocks and records, but there is no utility which scans schema for corruption.