Kbase P92653: Second truncate bi fails with error 5022, earlier truncate failed with error 9450 due to system full
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
On 1st truncate of Before Image file (BI), error 9450 due to system full
proutil <dbname> -C truncate bi
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)
<bkioWrite>:Insufficient disk space during <Write>, fd <file descriptor>, len <bytes>, offset <bytes>, file <dbname.bN >. (9450)
Fixed BI extents added to ensure no system full or BI limit on 2nd "truncate bi"
Error 5022 during 2nd truncate bi
SYSTEM ERROR: Ixundo failed in ixdel because it was unable to find the key to delete in index number <index number>. This Index may have an incorrect key. (5022)
CAUSE:
Crash recovery fails due to an index key missing for undoing a transaction; that index key was most likely removed on the previous undo, during the first truncate bi, but the bi note corresponding to this delete was missing in the BI due the insufficient disk space problem.
If a bi note "delete index key" is missing within the BI while the index key has been deleted within the index block, then an error 5022 is to be expected.
FIX:
Restore an earlier database backup.