FODC Panic due to memory corruption caused by invalid length
assignment in agent side data pulled from wire.
The db2diag.log messages example,
2018-07-23-09.04.12.019624-300 E12294432E1001 LEVEL:
Critical
PID : 13323 TID : 46997419583808 PROC :
db2sysc 0
INSTANCE: myinst1 NODE : 000 DB : MYDB
APPHDL : 0-56012 APPID:
AUTHID : MYUSERID HOSTNAME: myhostname
EDUID : 54044 EDUNAME: db2agent (MYDB) 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
"/home/myinst1/sqllib/db2dump/FODC_Panic_2018-07-23-09.04.11.999
848_
0000/". Please look in this directory for detailed
evidence about
what happened and contact IBM support if necessary to
diagnose the
problem.
2018-07-23-09.04.12.070112-300 E12295434E2388 LEVEL:
Severe
PID : 13323 TID : 46997419583808 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB
APPHDL : 0-56012 APPID:
AUTHID : MYUSERID HOSTNAME: myhostname
EDUID : 54044 EDUNAME: db2agent (MYDB) 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:999
MESSAGE : Memory validation failure, diagnostic file dumped.
DATA #1 : String, 28 bytes
Corrupt pool free tree node.
DATA #2 : File name, 40 bytes
13323.46997419583808.mem_diagnostics.txt
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002AAAB0C92574
_ZN13SQLO_MEM_POOL32diagnoseMemoryCorruptionAndCrashEmPKcb +
0x284
[1] 0x00002AAAB1C6C846
_ZN13SQLO_MEM_POOL10MemTreeGetEmmPP17SqloChunkSubgroupPj + 0x476
[2] 0x00002AAAB1C6D5B3
_ZN13SQLO_MEM_POOL19allocateMemoryBlockEmmjmPP17SqloChunkSubgrou
pPjP12SMemLogEvent + 0x53
[3] 0x00002AAAB1C6A643 sqlogmblkEx + 0xA53
[4] 0x00002AAAAF041422 _Z14sqlriSectSetupP8sqlrr_cbP9sqlri_shd
+ 0x142
[5] 0x00002AAAAEF3BC7D
_Z34sqlra_sqlW_get_dynamic_section_newP8sqlrr_cbP16sqlra_cached_
var + 0xC2D
[6] 0x00002AAAAEF03507
_Z14sqlra_load_varP8sqlrr_cbP16sqlra_cached_varP14SQLP_LOCK_INFO
Pb + 0x87
[7] 0x00002AAAAEF4E6E2 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ +
0xD42
[8] 0x00002AAAAEE22482
_Z13sqlrr_prepareP14db2UCinterfaceP16db2UCprepareInfo + 0x192
[9] 0x00002AAAADF6A4B3
_Z19sqljs_ddm_prpsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x863
[10] 0x00002AAAB1BDF106
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x3E6
[11] 0x00002AAAADF5C49B
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x36B
[12] 0x00002AAAADF56A9F
/home/db2insp1/sqllib/lib64/libdb2e.so.1 + 0x3486A9F
[13] 0x00002AAAADF54F1C
/home/db2insp1/sqllib/lib64/libdb2e.so.1 + 0x3484F1C
[14] 0x00002AAAADF51F69
/home/db2insp1/sqllib/lib64/libdb2e.so.1 + 0x3481F69
[15] 0x00002AAAADF51B5B
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xEB
[16] 0x00002AAAADC4F4DF _ZN8sqeAgent6RunEDUEv + 0xACF
.......
This being memory corruption. The stack might have different
functions based on the context of the environment. |
