Database crashes and shows following entries in db2diag.log:
2015-04-11-21.09.01.518729-240 I249706A489 LEVEL: Warning
PID : 60489826 TID : 22358 PROC : db2sysc
0
INSTANCE: xxxxxx NODE : 000 DB : XXXXXXXX
APPHDL : 0-18227 APPID: *LOCAL.DB2.150411071213
AUTHID : XXXXXXXXI
EDUID : 22358 EDUNAME: db2stmm (XXXXXXXX) 0
FUNCTION: DB2 UDB, Self tuning memory manager,
stmmResetStructureIfCorrupted, probe:2607
MESSAGE : STMM global benefit wall corrupted, reinitializing.
2015-04-11-21.09.01.553428-240 I250196A1619 LEVEL: Severe
PID : 60489826 TID : 33878 PROC : db2sysc
0
INSTANCE: xxxxxx NODE : 000 DB : XXXXX
APPHDL : 0-15790 APPID: *LOCAL.DB2.150411030258
AUTHID : XXXX
EDUID : 33878 EDUNAME: db2stmm (XXXXX) 0
FUNCTION: DB2 UDB, global services, sqlzAssertFailed, probe:10
DATA #1 : String, 116 bytes
ASSERTION FAILED!!!
ASSERTION EXPRESSION: fatal error in lock release.
SOURCE FILENAME: osslatch.C
LINE NUMBER: 110
DATA #2 : Hexdump, 8 bytes
0x0700000006FF9EB0 : 0700 0000 1000 0024 .......$
DATA #3 : Hexdump, 4 bytes
0x0700000010000024 : 0000 0000 ....
DATA #4 : Hexdump, 4 bytes
0x0700000006FF9E70 : FFFF FFFF ....
CALLSTCK:
[0] 0x0900000017E78094 pdLog + 0x88
[1] 0x090000001A324D40 sqlzAssertFailedValist + 0x144
[2] 0x0900000001F81830 ossAssertFailureAction + 0x130
[3] 0x0900000001F91F20 ossLockReleaseConflict + 0xA0
[4] 0x0900000001FCA9CC ossVLatchRelease + 0x6C
[5] 0x0900000019AA6884
stmmReleaseGlobalBenefitLatch__FP17stmmGlobalBenefit + 0x94
[6] 0x090000001785E4E8
stmmInitSharedMemorySegmentAndGlobalBenefit__FP17stmmGlobalBenef
it + 0x104
[7] 0x09000000178C3E94
stmmResetStructureIfCorrupted__FP17stmmGlobalBenefit + 0x414
[8] 0x09000000178C317C
stmmUpdateGlobalBenefit__FP17stmmGlobalBenefitP16sqeLocalDatabas
edPb + 0x88
[9] 0x09000000178C050C
stmmGetDBMemDataAutomatic__FPP21stmmCostBenefitRecordP19stmmDBMe
mTuningInfoP19stmmExternalBenefitP16sqeLocalDatabase + 0x204
Failed assert in ossLockReleaseConflict is caused by the timing
hole in the latch, which protects STMM Global Benefit Data. |
