Personal tools
You are here: Home DB2 Problem Resolution Locking errors Dlconn for event monitor DB2DETAILDEADLOCK - MAXLOCKS
Navigation
Log in


Forgot your password?
 
Document Actions

Dlconn for event monitor DB2DETAILDEADLOCK - MAXLOCKS

Dlconn for event monitor DB2DETAILDEADLOCK truncated by 134065 bytes! Deadlock ID: 25 Participant:1 Original locks in list: 807. Redefine the event monitor, increasing the BUFFERSIZE by 33 pages. Increase DIAGLEVEL to 4 to see the truncated Locks in this log. Set MAXLOCKS parameter to 98 to fix this problem

A - Error


DIAG ERROR:


INSTANCE: db2inst1             NODE : 000         DB   : CCA_TBC
APPHDL  : 0-355                APPID: 10.210.55.14.51999.091104120350
AUTHID  : USRDTS 
FUNCTION: DB2 UDB, database monitor, sqm___log_event, probe:41
DATA #1 : String, 262 bytes
Dlconn for event monitor DB2DETAILDEADLOCK truncated by 134065 bytes!
 Deadlock ID: 25 Participant:1 Original locks in list: 807.
 Redefine the event monitor, increasing the BUFFERSIZE by 33 pages.
 Increase DIAGLEVEL to 4 to see the truncated Locks in this log.

COMMAND LINE ERROR:

CCA_TBC,0: [IIS-CONN-DB2-000004] DB2 function SQLExecute failed:  SQLSTATE = 40001: Native Error Code = -911: Msg = [IBM][CLI Driver][DB2/LINUXZ64] SQL0911N  The current transaction has been rolled back because of a deadlock or timeout.  Reason code "68".  SQLSTATE=40001 (CC_DB2DBStatement::executeUpdate, file CC_DB2DBStatement.cpp, line 797)


B - Possible Causes


The MAXLOCKS db cfg parameter is set to low value.


C - Solution


Increase the MAXLOCKS parameter to value 98

db2 update db cfg for db <DBNAME> using MAXLOCKS 98 immediate

Security Awareness
Would you like your company to implement gamification into your security awareness program?





Polls