suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT15136 Status: Closed

DB2 INSTANCE MAY PANIC IN SQLBSETNUMSLOTSANDNBPFORNEWRTBPDEF WHEN STMM IS
ON

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2 instance may panic in sqlbSetNumSlotsAndNBPForNewRTBPDef 
when STMM is on 
 
From db2diag.log 
----- 
2016-02-17-13.17.55.785800+540 I3208063A628         LEVEL: 
Severe 
PID     : 39583928             TID : 49779          PROC : 
db2sysc 0 
INSTANCE: XXXXXXX              NODE : 000           DB   : 
XXXXXX 
APPHDL  : 0-60951              APPID: XXXXXXXX.XXXX.160308034136 
AUTHID  : P322704              HOSTNAME: XXXXXXXXXXXX 
EDUID   : 49779                EDUNAME: db2agent (TPMSDB) 0 
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:1598 
DATA #1 : String, 67 bytes 
sqlbSetNumSlotsAndNBPForNewRTBPDef: max numPages has been 
exceeded! 
DATA #2 : Hexdump, 4 bytes 
0x0A00000016FF4120 : FD76 9656 
.	v.V 
 
2016-02-17-13.17.55.844350+540 E3208692A973         LEVEL: 
Critical 
PID     : 39583928             TID : 49779          PROC : 
db2sysc 0 
INSTANCE: XXXXXXX              NODE : 000           DB   : 
XXXXXX 
APPHDL  : 0-60951              APPID: XXXXXXXX.XXXX.160308034136 
AUTHID  : P322704              HOSTNAME: XXXXXXXXXXXX 
EDUID   : 49779                EDUNAME: db2agent (XXXXXX) 0 
FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, 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 
          "/db2dump/FODC_Panic_2016-02-17-13.17.55.803963_0000/" 
          . Please look in this directory for detailed evidence 
about what 
          happened and contact IBM support if necessary to 
diagnose the 
          problem. 
 
----- 
 
The associated stack trace file, has similar as below: 
----- 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000534F94 pthread_kill + 0xD4 
0x0900000009B9EAE4 sqloDumpEDU + 0x6C 
0x0900000009978B90 sqle_panic__Fv + 0x208 
0x0900000009DA35A8 sqlb_panic + 0x50 
0x090000000B90E150 
sqlbSetNumSlotsAndNBPForNewRTBPDef__FP13SQLO_MEM_POOLP10sqlf_dbc 
fdP15SQLB_BufferPooliUi + 0x74C 
0x090000000B90C304 
sqlbInitRegularRuntimeBPDefs__FP13SQLO_MEM_POOLP10sqlf_dbcfdP18S 
QLB_RuntimeBPDefsP17SQLB_OnDiskBPDefsP8sqeAgent + 0x1B4 
0x090000000B90B218 
sqlbInitOnDiskAndRTBPDefs__FP13SQLO_MEM_POOLP10sqlf_dbcfdPcT3PP1 
7SQLB_OnDiskBPDefsPP18SQLB_RuntimeBPDefsP8sqeAgentUl + 0x538 
0x090000000B91342C 
sqlbGetTotalSQBMemSize__FP8sqeAgentP10sqlf_dbcfdPcN23bPUlT7 + 
0xC7C 
0x090000000B6D4E34 
@82@sqleCalculateDbHeaps__FP9sqlf_kcfdP10sqlf_dbcfdP8SQLE_BWAP8s 
qeAgentCcCbCPUlT7P22SqloMemPoolReservation + 0x170 
0x090000000AC29C8C 
FirstConnect__16sqeLocalDatabaseFP8SQLE_BWARcP8sqeAgentP8sqlo_gm 
tiT5Pb + 0x13BC 
0x090000000AEA7690 
StartUsingLocalDatabase__8sqeDBMgrFP8SQLE_BWAP8sqeAgentRccP8sqlo 
_gmtPb + 0x1728 
0x090000000AECC248 
AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc 
+ 0x36C 
0x090000000ADCB8E4 
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4C8 
0x090000000ADCA6B0 sqlelostWrp__FP14db2UCinterface + 0x3C 
0x090000000ADCA3E0 sqleUCengnInit__FP14db2UCinterfaceUs + 0x294 
0x090000000ADEB9D4 sqleUCagentConnect + 0x2A4 
0x090000000ADE917C 
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1B0 
0x090000000ADE7DB8 
sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x394 
0x090000000ADE7764 
sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte 
rface + 0x5C 
0x090000000ADE7354 
.sqljsParse.fdpr.clone.71__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s 
qeAgentb + 0xF4 
0x090000000B239CFC @73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2D8 
0x090000000AC37B14 
@73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
0x090000000AC3856C 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x558 
0x090000000AC377E0 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x21C 
0x090000000AF9DECC RunEDU__8sqeAgentFv + 0x590 
0x090000000AF99AE0 EDUDriver__9sqzEDUObjFv + 0x13C 
0x090000000AF99968 sqlzRunEDU__FPcUi + 0x10 
0x090000000AFB7864 sqloEDUEntry + 0x264 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Turn off STMM.
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.05.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)