Kbase 21163: Starting Database Gives Error (3837) and (3836)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Solution ID: 21163
SYMPTOM(s):
Database fails to start with errors.
rmDoDif: overrun got <size> had <size> (3837)
SYSTEM ERROR: rmflchg: RECID rmDoDif returns , expected (3836)
CAUSE:
There is a mismatch in the RM-table (RM chain) about the registered free space available in one of the blocks and the actual (real) free space in this block.
FIX:
Rebuild the RM table so the registered free space and the actual free space in the block are equal. In order to do this, DBRPR must be run. Before this is possible, the bi must be truncated. However, this will fail with the same errors (3837 and 3836). Using the force option (-F) also fails. At his point, 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.
Remember, forcing into a Database is never recommended. In these situations, going to backup should be the first option.
To use -F to force into the DBRPR Menu:
proutil sports -C dbrpr -F
Select 1. Database Scan Menu.
Then Select:
7: Rebuild free chain
8: rebuild RM chain
-> GO
If the database still won't start, restore from backup. If the database does start, it should be dumped and loaded as soon as possible.