|
Problem IT19402
|
Status: Closed |
PURESCALE MEMBER CAN CRASH IN PDDUMPVALISTELEMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Purescale Member can crash in pdDumpValistElement.
db2diag.log:
2016-08-09-20.29.15.013342+120 E9513081A818 LEVEL: Error
PID : 6291898 TID : 464755 PROC :
db2sysc 3
INSTANCE: db2inst1 NODE : 003 DB :
SICDBTST
APPHDL : 3-45717 APPID: *N3.db2inst1.160809182916
AUTHID : DB2INST1 HOSTNAME: pshost4
EDUID : 464755 EDUNAME: db2agent (MYDBNAME) 3
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:30
MESSAGE : ADM14005E The following error occurred: "Trap".
First Occurrence
Data Capture (FODC) has been invoked in the following
mode:
"Automatic". Diagnostic information has been recorded
in the
directory named
"/db2inst1/db2/db2diag/DIAG0003/FODC_Trap_2016-08-09-20.29.15.0
10099
_6291898_464755_003/".
2016-08-09-20.29.15.186025+120 I9513900A605 LEVEL: Error
PID : 6291898 TID : 464755 PROC :
db2sysc 3
INSTANCE: db2inst1 NODE : 003 DB :
SICDBTST
APPHDL : 3-45717 APPID: *N3.db2inst1.160809182916
AUTHID : DB2INST1 HOSTNAME: pshost4
EDUID : 464755 EDUNAME: db2agent (MYDBNAME) 3
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:1
MESSAGE : Error in agent servicing application with coor_node:
DATA #1 : Hexdump, 2 bytes
0x0A0000019FC0E520 : 0003
..
The stack can look like the following:
<StackTrace>
-------Frame------ ------Function + Offset------
0x000000000000F4F8 ?unknown + 0x0
0x09000000068A51C8
.pdDumpValistElement.fdpr.clone.4405__24PDComponentEventRecorder
FPPcPCvT2CUl + 0x19C
0x09000000068A4F20
.recordEventInternal.fdpr.clone.520__26PDComponentEventRecorderE
xFCUiCUlT1T2PPc + 0x2B0
0x09000000068A4BF8
recordEvent__26PDComponentEventRecorderExFCUiCUlT2e + 0x74
0x0900000006062E20
SAL_ReadAndRegisterMultiple__14SAL_GBP_HANDLEFP12SQLB_GLOBALSP14
SAL_RAR_PARAMSCUlCPUiT4CUiT3 + 0x1D74
0x0900000005A6EF8C
sqleSCAReadMultiple__FP11SQLE_SCA_CBUlP14SAL_RAR_PARAMS + 0xAC
0x0900000005A6F980
sqlpxSDListIndoubtTransactions__FP8sqeAgentP18db2XaRecoverStruct
PiT3 + 0x500
0x0900000008100028
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x6AB50
0x090000000802E26C
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0xF50
0x09000000080144FC sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo +
0x610
0x09000000063307A0
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x568
0x0900000006339D1C @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x14A8
0x0900000006339D1C @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x14A8
0x0900000006339910 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x109C
0x090000000537F2C4
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
0x090000000537FDD4
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8
0x09000000056013C8 RunEDU__8sqeAgentFv + 0x4C05C
0x0900000005640E40 RunEDU__8sqeAgentFv + 0x120
0x0900000006B85348 EDUDriver__9sqzEDUObjFv + 0x134
0x0900000005DD48D8 sqloEDUEntry + 0x390
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
Note that the customer can disable SAL event recording and
should be able to avoid this trap until a fix is provided.:
db2pd -dmpEvRec name=SALER_LF stop
db2pd -dmpEvRec name=SALER_HF stop
db2pd -dmpEvRec query
NOTE: Will need to run the above if the Member is
stopped/started. |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.02.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
