When the problem happens, information similar to the following
will be seen in db2diag.log:
===========================================
2010-01-01-01.01.01.123456+000 I12345678901234 LEVEL: Severe
PID : 1234567 TID : 12345 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-123 APPID: *N0.db2inst1.1001010101012
AUTHID : DB2INST1
EDUID : 12345 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:10
MESSAGE : Possible memory corruption detected.
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
0x820F0002
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8
bytes
0x000000012d87e1e0
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x000000012D87E1C8 : 0000 0001 2D87 DA6C 56C3 B357 253D 0471
....-..lV..W%=.q
0x000000012D87E1D8 : FAB0 0000 0012 D860
.......`
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x000000012D87E1E0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x000000012D87E1F0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x000000012D87E200 : 0046 5F4E 495F 4549 425F 504C 5F42 534E
.F_NI_EIB_PL_BSN
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x090000000B88EAB8 pdLog + 0xC0
[1] 0x090000000AAF45B0
@78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0x150
[2] 0x090000000B24FD58 sqlofmblkEx + 0x48C
[3] 0x090000000B69955C sqlofmblkEx@glue801 + 0x78
[4] 0x090000000C009074
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x1A8
[5] 0x090000000B8D13F4
.sqljs_ddm_excsqlstt.fdpr.clone.149__FP14db2UCinterfaceP13sqljDD
MObject + 0xC0
[6] 0x090000000B7C6A48
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0xEC
[7] 0x090000000B7C6DE4
.sqljsParse.fdpr.clone.120__FP13sqljsDrdaAsCbP14db2UCinterfaceP8
sqeAgentb + 0x268
[8] 0x090000000B7C5AA0
@63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x290
[9] 0x090000000B9054D0
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xEC
2010-01-01-01.01.01.123457+000 I12345678901234 LEVEL: Severe
PID : 1234567 TID : 12345 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-123 APPID: *N0.db2inst1.1001010101012
AUTHID : DB2INST1
EDUID : 12345 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, 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
"/db2home/sqllib/db2dump/FODC_Panic_2010-01-01-01.01.01.123456_0
000/"
. Please look in this directory for detailed evidence
about what
happened and contact IBM support if necessary to
diagnose the
problem.
===========================================
The problem could be encountered by various kinds of operations
that manipulate LOB data with locators, and one or more of the
LOB locates is NULL. One known operation is LOAD. |
