Kbase P141182: Getting error 860 when truncating a bi file after previous failed attempts and clean up of a dead us
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/02/2011 |
|
Status: Verified
SYMPTOM(s):
Getting error 860 when truncating a bi file after previous failed attempts and clean up of a dead user.
SYSTEM ERROR: rlmemchk mb_lasttask: note=<number> mstrblk=<number>. (860)
Stack trace from _proutil reads: (Associated with second truncation attempt)
rlredo
dorollf
warmstrt
Received 3839 and 3841 errors when truncating the bi file prior to this latest attempt to truncate the bi file.
Stack trace from _proutil reads: (Associated with first truncation attempt)
seqInit
dbSetOpen
error reading record (3839)
error -1218 reading record 10127 (3839)
SYSTEM ERROR: error loading sequence cache (3841)
Database log file shows that there was an abnormal database shutdown prior to the first attempt to truncate the bi file.
The database shutdown abnormally when disconnecting a dead user.
Begin ABNORMAL shutdown code (2249)
Disconnecting dead user <number>. (2527)
User that died was in the process of backing out transactions.
SYSTEM ERROR: Releasing regular latch. latchId:<latch-num> (5028)
User <num> died holding <num> shared memory locks. (2522)
FACT(s) (Environment):
Multiple user processes backing out transactions simultaneously.
There were other errors reported in the database log file prior to the abnormal shutdown dealing with the lock table and lkrels.
SYSTEM ERROR: lkrels record <recid> not locked. (435)
Lock table overflow, increase -L on server (915)
Sun Solaris SPARC 32-bit
IBM AIX
Progress 9.1E
CAUSE:
There is corruption in the bi file.
FIX:
Restore the database from a good backup.
If your site makes use of After Imaging (AI), roll forward appropriate ai files to bring database back to a consistent state.