Instance may crash with below stack traceback
recorded in db2diag.log. The message indicates
the panic is due to attempting to unlock an
invalid latch. Analysis shows this latch to be
the coordCBLatch.
This is a timing issue that can lead to a panic
or trap on a heavy workload system in an XA
environment.
-----
2014-04-24-21.14.38.310552+540 E13493828 LEVEL: Severe (OS)
PID : 2645 TID : 14000 PROC : db2sysc 0
INSTANCE: db2inst NODE : 000 DB : DB2
APPHDL : 0-27372 APPID: 192.168.0.1.35507.14038
AUTHID : db2inst HOSTNAME: panipuri
EDUID : 452 EDUNAME: db2agent (DB2) 0
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::releaseConflict, probe:330
MESSAGE :
ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
"expected latch to be held."
CALLED : OS, -, unspecified_system_function
DATA #1 : String, 39 bytes
Attempting to unlock an invalid latch:
DATA #2 : File name, 16 bytes
sqloLatchCAS64.C
...snip...
CALLSTCK: (Static functions may not be resolved correctly...
[0] ... pdLogSysRC + 0x45B
[1] ... _ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKc...
[2] ... _ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x354
[3] ... /home/db2zadm/sqllib/lib64/libdb2e.so.1 + 0x415C8...
[4] ... _ZN8sqeAgent14InterruptAgentEhj + 0xFD0
[5] ... _Z24sqleInterruptApplicationP19SQLE_COORDINATOR_C...
[6] ... _Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXI...
[7] ... _Z12sqlrrbck_dpsP8sqlrr_cbiiiP15SQLXA_CALL_INFOP9...
[8] ... _Z8sqlrrbckP8sqlrr_cbiiiiP15SQLXA_CALL_INFO + 0x268
[9] ... _Z15sqlrr_xrollbackP14db2UCinterface + 0x459
[10] ... _Z17sqljsSyncRollbackP14db2UCinterface + 0x173
[11] ... _Z17sqljs_ddm_syncctlP14db2UCinterfaceP13sqljDDM...
[12] ... _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqlj...
[13] ... _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP...
[14] ... /home/db2zadm/sqllib/lib64/libdb2e.so.1 + 0x147E920
[15] ... /home/db2zadm/sqllib/lib64/libdb2e.so.1 + 0x147D72F
[16] ... /home/db2zadm/sqllib/lib64/libdb2e.so.1 + 0x147B513
[17] ... _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xF3
[18] ... _ZN8sqeAgent6RunEDUEv + 0x70A
[19] ... _ZN9sqzEDUObj9EDUDriverEv + 0xF3
[20] ... _Z10sqlzRunEDUPcj + 0x9
[21] ... sqloEDUEntry + 0x29F
[22] ... /lib64/libpthread.so.0 + 0x77F1
[23] ... clone + 0x6D
2014-04-24-21.14.38.755376+540 E1349732 LEVEL: Critical
PID : 2645 TID : 144115200 PROC : db2sysc 0
INSTANCE: db2inst NODE : 000 DB : DB2
APPHDL : 0-27372 APPID: 192.168.0.1.35507.4121438
AUTHID : db2inst HOSTNAME: panipuri
EDUID : 452 EDUNAME: db2agent (DB2) 0
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
MESSAGE : ADM14001C
An unexpected and critical error has occurred: "Panic".
The instance may have been shutdown as a result. "Automatic"
FODC (First Occurrence Data Capture) has been invoked and
diagnostic information has been recorded in directory
"/FODC_Panic_2014-04-24-21.14.38.720919_0000/".
An alternate trap file is:
4 sqloEDUCodeTrapHandler
5 __PRETTY_FUNCTION__.5889
6 sqeAgent::InterruptAgent
7 sqleInterruptApplication
8 sqlpxrbk
9 sqlrrbck_dps
10 sqlrrbck
11 sqlrr_xrollback
12 sqljsSyncRollback
----- |
