SAP Knowledge Base Article - Preview

2824968 - Db6 lock event monitor SQLP_LTIMEOUT caused database shutdown


Abnormal database shutdown is seen after the following message in db2diag.log:

2019-02-06- I43829055E798 LEVEL: Severe
PID : 60000 TID : 17723710959968 PROC
: db2sysc 0
INSTANCE: db2inst NODE : 004 DB : SAMPLE
APPHDL : 0-6383 APPID: xxxxxxxxxxxxxxx
AUTHID : xxxxxxxxxxxx HOSTNAME: node1
EDUID : 51111 EDUNAME: db2agnta (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldCriticalSectionEnd, probe:128
CALLED : DB2 UDB, data management, sqldProtectPendAct
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT
                "LockTimeOut - tran rollback Reason code 68"
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0000000000000000 ?unknown + 0x0
[1] 0x0000000000000000 ?unknown + 0x0

This issue only occurs when a lock wait event monitor is being used.



Db2 Linux, Unix and Windows 11.1


SAP NetWeaver 7.3


APAR, IBM, MON_LOCKWAIT, shutdown, fp4, , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.