Kbase P88837: Database down with errors 915 and 6495
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/12/2008 |
|
Status: Verified
SYMPTOM(s):
Database down with errors 915 and 6495
Begin transaction backout. (2252)
Lock table overflow, increase -L on server (915)
Out of free shared memory. Use -Mxs to increase. (6495)
SYSTEM ERROR: mtlatch <latch-num>, holding <lock>. (3712)
SYSTEM ERROR: Releasing regular latch. latchId:<latch-num> (5028)
SYSTEM ERROR: Releasing multiplexed latch. latchId:<latch-num> (5029)
User <num> died holding <num> shared memory locks. (5026)
Lots of 915 6495 error messages in the database log file before database went down
FACT(s) (Environment):
Client session sends SIGINT CTRL+C
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
Bug# OE00103069
CAUSE:
Fail to handle properly the rollback of the program without enough free shared memory. When 915 errors happens, the database engine tries to supply more slots from "-Mxs to -L" in order to try to complete request without blowing up the -L table at the first place. Due to many 915 errors within a same time, the -Mxs is blown up, which is the fatal error for a database engine.
FIX:
As a workaround, increase -L database startup parameter and review the program(s) concerned to verify that that the number of Record Locks being used is reasonable.