The db2fmp executed from db2expln may crash or hang.
For both those cases, db2explan looks like hanging.
1. If db2fmp crashes, the following kind of records are logged
in db2diag.log.
The db2fmp process may crash with the memory error.
The following kind of errors can be observed in db2diag.log for
this issue.
2012-01-17-16.48.14.413218+540 E609326A846 LEVEL:
Critical
PID : 2015418 TID : 1 PROC : db2fmp
(34274) 0
INSTANCE: db2inst1 NODE : 000
APPID : xxx.xxx.x.x.xxxxx.xxxxxxxxxxxx
EDUID : 1 EDUNAME: db2fmp (34274) 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/db2inst1/sqllib/db2dump/". Please look in this
directory for
detailed evidence about what happened and contact IBM
support if
necessary to diagnose the problem.
2012-01-17-16.48.14.416264+540 E610173A1356 LEVEL: Severe
PID : 2015418 TID : 1 PROC : db2fmp
(34274) 0
INSTANCE: db2inst1 NODE : 000
APPID : xxx.xxx.x.x.xxxxx.xxxxxxxxxxxx
EDUID : 1 EDUNAME: db2fmp (34274) 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, 29 bytes
2015418.1.mem_diagnostics.txt
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000004B5E148 pdLog + 0xA8
[1] 0x0900000004BFD374
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb +
0x2A8
[2] 0x0900000004BFCFF4
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb@glue3
69 + 0x7C
[3] 0x0900000005DA99D8
.MemTreePut.fdpr.clone.118__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC
hunkSubgroup + 0xF4
[4] 0x0900000004DCC448 sqlofmblkEx + 0x264
[5] 0x090000001F6DB110 sqlngFPGCleanup__FR13sqlngFPGState +
0xF0
[6] 0x090000001F6C161C displayGraph__FR10RunOptions + 0x17C
[7] 0x090000001F6CA4F4 processSection__FR10RunOptions + 0x954
[8] 0x090000001F6C445C
processPackage__FR10RunOptionsPcN22P7sqlchar + 0x16FC
[9] 0x090000001F6BFA8C doExplain__FR10RunOptions + 0xF2C
2. If db2fmp hangs, the following kind of stack trace is
observed
for db2fmp.
(dbx) where
findParentsPointer__8SMemNodeFPP8SMemNode(??, ??) at
0x900000002215b28
removeFromPool__22SqloExtraChunkSubgroupFv(??) at
0x900000002215bf8
sqlofmblkEx.fdpr.chunk.12(??) at 0x90000000221d120
memCleanup__FR10RunOptionsl(0xfffffffffffe488, 0x1) at
0x90000000bd4b50c
explain(??, ??, ??, ??) at 0x90000000bd468c8
@76@sqlerRunRoutine.fdpr.chunk.1__FP13sqleInvokerCBPi(??, ??) at
0x900000001ab6b7c
sqlerDyload.fdpr.chunk.6(??, ??) at 0x900000002241f90
sqlerFmpListener.fdpr.chunk.24(??, ??, ??, ??, ??) at
0x900000002231978
main(??, ??) at 0x100001214 |
