Kbase P23052: Database crashes for shared memory user with (49) (5072) (2249)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/04/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
FACT(s) (Environment):
SCO Unixware 7.1.1
SYMPTOM(s):
SYSTEM ERROR: Memory violation. (49)
User <num> died with 1 buffers locked. (5027)
Begin ABNORMAL shutdown code 2 (2249)
8 processors PIII Xeon 700Mhz with 2Mb cache
User was running an invoicing program, that accesses many tables
The process was also outputting a stream to a text file
No associated hardware errors in the syslogs at the time of crash
stack trace from _progres reads
uttrace
utcore
drexit
msgout
msgnCB
msgCB
dsmFatalMsgnCallBack
CAUSE:
The WDOG detected that buffer latches (locks) were left in an inconsistent state, possibly due to the user process aborting as a result of system error (49), which lead to the broker shutting down the database to protect its integrity.
The process was running an update on many tables concurrently which have been associated with index corruption. The output text file may have also been associated with the system error, although there was no evidence of hardware errors in the system logs at the time. The finite cause is not known at the time of writting.
FIX:
truncate the database and then proserve it, if crash recovery completes without error, the database is ready for normal use, otherwise the hotspare or backup database will need to be restored.