DB2 - Problem description
| Problem IC98077 | Status: Closed |
DB2 INSTANCE MIGHT CRASH AFTER REPORTING 'CM PARAMETER BAD' ERROR. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
The ADM14001C will be raised due to memory corruption after
receiving incorrect packet data, which is reported in
db2diag.log via "CM parameter bad" severe error. While
processing the error an internal buffer is overwritten. DB2
instance will crash when tried to free that corrupted buffer.
Related error messages in db2diag.log:
2014-01-03-12.13.04.720065+120 I288704A1499 LEVEL: Severe
PID : 13515174 TID : 28572 PROC : db2sysc
0
INSTANCE: insta1 NODE : 000 DB : datab1
APPHDL : 0-13534 APPID:
112.154.3.224.51543.131007124205
AUTHID : AUTH1
EDUID : 28572 EDUNAME: db2agentg (datab1) 0
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive,
probe:30
MESSAGE : ZRC=0x81360010=-2127167472=SQLZ_RC_CMPARM, SQLT_SQLJC
"CM parameter bad"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 8 bytes
68
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000007000AB8 pdLog + 0xC0
[1] 0x09000000071E72E4
sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35 + 0x234
[2] 0x09000000071E6FDC
sqljcLogCCIError__FP10sqljCmnMgrPCcP12SQLCC_COND_TUclN35@glueDCB
+ 0x78
[3] 0x0900000006A298B4 sqljcIntReceive__FP10sqljCmnMgr + 0x1C0
[4] 0x0900000007046BC4
sqljcReadGetPtrInt__FP10sqljCmnMgrPPUcPl + 0x114
[5] 0x0900000007FD09B8
sqljrParseExtDta__FP14db2UCinterfaceP15sqljrParserInfo13sqljrRqs
tType + 0xA4
[6] 0x0900000009C251B4
sqljrParseOpenSuccessReply__FP14db2UCinterfaceUsP8db2UCpidP14db2
UCRtnResSet + 0x6580
[7] 0x0900000009C3D5EC
sqljrParseOpenQueryReply__FP14db2UCinterface + 0x980
[8] 0x0900000007FC4884 sqljrParse__FP14db2UCinterface + 0x2AC
[9] 0x0900000008079838
sqljrDrdaArOpen__FP14db2UCinterfaceP15db2UCCursorInfo + 0x568
2014-01-03-12.13.54.391640+120 E296128A969 LEVEL:
Critical
PID : 13515174 TID : 28572 PROC : db2sysc
0
INSTANCE: insta1 NODE : 000 DB : datab1
APPHDL : 0-23548 APPID:
112.154.3.224.45490.131007124309
AUTHID : AUTH1
EDUID : 18572 EDUNAME: db2agentg (datab1) 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/insta1/sqllib/db2dump/FODC_Panic_2014-01-03-12.13.54.3796
47_00
00/". Please look in this directory for detailed
evidence about what
happened and contact IBM support if necessary to
diagnose the
problem.
Below stack trace led to the crash:
Stack #1 Signal #11 Timestamp
2013-10-07-14.43.50.489075
0 sqloCrashOnCriticalMemoryValidationFailure
1 SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
2 SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
3
.MemTreePut.fdpr.clone.224__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC
hunkSubgroup
4 sqlofmblkEx
5 sqlcctcpfreebuffer
6 sqlccfreebuffer
7 sqlccfreebuffer
8 sqljcCmnMgrTerm
9 sqljsTerm
10 @63@sqljsCleanup
11 @63@sqljsDrdaAsInnerDriver
12 sqljsDrdaAsDriver
13 sqeAgent::RunEDU
14 sqzEDUObj::EDUDriver
15 sqloEDUEntry | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 10.5.4. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
| Solution | |
Upgrade to 10.5.4. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.12.2013 15.09.2014 15.09.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.4 |
|