Kbase P86863: Database crashes after error 915 and 3712
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/7/2011 |
|
Status: Verified
SYMPTOM(s):
Database crashes after error 915 and 3712
Lock table overflow, increase -L on server (915)
Begin transaction backout. (2252)
Transaction backout completed. (2253)
SYSTEM ERROR: mtlatch <latch-num>, holding <lock>. (3712)
SYSTEM ERROR: mtlatch 7, holding 0x40. (3712)
** Save file named core for analysis by Progress Software Corporation. (439)
SYSTEM ERROR: Releasing regular latch. latchId:<latch-num> (5028)
SYSTEM ERROR: Releasing multiplexed latch. latchId:<latch-num> (5029)
Begin ABNORMAL shutdown code (2249)
database log file shows error 915 right before error 3712
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1x
CAUSE:
Bug# OE00098824
FIX:
Upgrade to OpenEdge 10.0A or later. OpenEdge 10.0A introduces a private latch for each table chain instead of a single latch controlling access to the all the table chains and this implementation prevents this issue from happening.
If upgrading to OpenEdge is not an option at this time you can work around the issue by increasing the -L parameter or decreasing the locks needed so that no error 915 is triggered.
To decrease the number of locks needed:
. review the transactions within the application
. consider changing the isolation level of ODBC clients to READ UNCOMMITTED for using less locks.