Kbase P6619: Database startup fails with 3834 error
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/03/2005 |
|
Status: Unverified
SYMPTOM(s):
Database startup fails with error
SYSTEM ERROR: rmdochg: size <rec-size>, expected <rec-size> (3834)
CAUSE:
This is a known issue being investiaged by development. The record change size in the note does not match the record change size of what is on disk.
FIX:
Method 1: Restore the Database from backup and apply the after image files.
Method 2: Rebuild the RM table so the registered free space and the actual free space in the block are equal.
To rebuild the RM table perform the following:
1. Truncate the before image file
Syntax: proutil dbname -C truncate BI
2. Run DBRPR
Syntax: proutil dbname -C dbrpr
Select 1. Database Scan Menu.
Then Select:
7: Rebuild free chain
8: rebuild RM chain
A: Apply to all areas
G: GO
If the truncation of the BI file fails it is strongly recommended the database be restored from backup. The -F option is provided as a last resort emergency measure and should never be needed. This parameter is made available to allow you to extract and salvage as much data as possible from a database that is damaged and otherwise unusable. It should be used only when the alternative is loss of the entire database. It cannot be stressed strongly enough that using ?F must be considered as the very last resource. Going back to a backup is the safest option. For further information on the -F option See Solution: P24330
Use the Force option with DBRPR. This has the same effect as using the Force option with truncating the .bi. The database, is marked as damaged.
To use -F to force into the DBRPR Menu:
Syntax: proutil sports -C dbrpr -F
Select 1. Database Scan Menu.
Then Select:
7: Rebuild free chain
8: rebuild RM chain
A: Apply to all areas
G: GO
Dump and load the database as soon as possible.