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 IC88707 Status: Closed

INSTANCE/DATABASE MIGHT ABEND DURING THE COLLECT OF EVENT DETAIL S IN
SQMFASTWRITERQUEUEMGR::RELEASEFASTWRITERRECORDSTOPOOL.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Instance/Database might abend during the collect of Event 
Details in 
sqmFastWriterQueueMgr::releaseFastWriterRecordsToPool. 
 
db2diag.log: 
 
2012-07-25-08.25.37.811546+120 I3021206E595        LEVEL: Error 
PID     : 31303                TID  : 140706383390464PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-28447              APPID: 
*LOCAL.DB2.120831065143 
AUTHID  : DB2INST1 
EDUID   : 215                  EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, database monitor, 
sqmLockEvents::collectLockOwnerRecord, probe:2268 
MESSAGE : ZRC=0x8B0F000B=-1961951221=SQLO_NOMEM_MONH 
          "No memory available in 'Database Monitor Heap'" 
          DIA8300C A memory heap error has occurred. 
 
2012-07-25-08.25.37.811943+120 I3021802E2007       LEVEL: Severe 
PID     : 31303                TID  : 140706383390464PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-28447              APPID: 
*LOCAL.DB2.120831065143 
AUTHID  : DB2INST1 
EDUID   : 215                  EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x0000000200001d68 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x0000000200001D50 : 0000 0000 0100 0000 0000 0000 0200 0000 
................ 
0x0000000200001D60 : B002 0000 0200 0000 
........ 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x0000000200001D68 : 0000 0000 0000 0000 281D 0000 0200 0000 
........(....... 
0x0000000200001D78 : 0000 0100 0200 0000 FFFF FFFF 0000 0000 
................ 
0x0000000200001D88 : 0C20 8000 2C01 0000 8905 0000 0100 0000 
. ..,........... 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007FFFF322F996 pdLog + 0x398 
  [1] 0x00007FFFF4D92AB8 
/home/db2root1/sqllib/lib64/libdb2e.so.1 + 0x28C4AB8 
  [2] 0x00007FFFF5AFD526 sqlofmblkEx + 0x9A6 
  [3] 0x00007FFFF34ADE8E 
_ZN21sqmFastWriterQueueMgr30releaseFastWriterRecordsToPoolEP12sq 
zDataChainI19sqmFastWriterRecordE + 0x6C 
  [4] 0x00007FFFF43FC986 
_ZN13sqmLockEvents22collectLockOwnerRecordEP9sqeBsuEdujjP14SQLP_ 
LOCK_INFO + 0x148 
  [5] 0x00007FFFF38011B6 
_Z8sqlplnfdP9sqeBsuEduP14SQLP_LOCK_INFOP8SQLP_LCBP9SQLP_LHSHP8SQ 
LP_LRBjimiP8SQLP_AWBi + 0x24D6 
  [6] 0x00007FFFF5B0D6C1 _Z7sqlplrqP9sqeBsuEduP14SQLP_LOCK_INFO 
+ 0xFED 
  [7] 0x00007FFFF5AA7D58 _Z12sqldReadNormP13SQLD_DFM_WORKl + 
0xEC6 
  [8] 0x00007FFFF5AA5EAE 
/home/db2root1/sqllib/lib64/libdb2e.so.1 + 0x35D7EAE 
  [9] 0x00007FFFF5AA4A50 _Z7sqldfrdP13SQLD_DFM_WORK + 0xAA 
 
Possible Trap Stack: 
 
0x00007FFFF2033377 ossDumpStackTraceEx 
0x00007FFFF202E136 OSSTrapFile 
0x00007FFFF4D58367 sqlo_trce 
0x00007FFFF4D9F025 sqloEDUCodeTrapHandler 
0x00007FFFF7BD05D0 address: 0x00007FFFF7BD05D0 ; dladdress: 
0x00007FFFF7BC1000 
0x00007FFFF379373E SqloChunkSubgroupisValid 
0x00007FFFF4D93069 sqloMemSearchForChunkSubgroupHeadermb 
0x00007FFFF4D92CA7 address: 0x00007FFFF4D92CA7 ; dladdress: 
0x00007FFFF24CE000 
0x00007FFFF5AFD526 sqlofmblkEx 
0x00007FFFF34ADE8E sqmFastWriterQueueMgr 
0x00007FFFF43FC986 sqmLockEvents 
0x00007FFFF38011B6 sqlplnfd 
0x00007FFFF5B0D6C1 sqlplrq 
0x00007FFFF5AA7D58 sqldReadNorm 
0x00007FFFF5AA5EAE address: 0x00007FFFF5AA5EAE ; dladdress: 
0x00007FFFF24CE000 
0x00007FFFF5AA4A50 sqldfrd 
0x00007FFFF5A9A814 sqldRowFetch 
0x00007FFFF5B324DD sqlritaSimplePerm 
0x00007FFFF3927B06 sqlrihsjn 
0x00007FFFF3900D0F sqlriExecThread 
0x00007FFFF3927F89 sqlrihsjn 
0x00007FFFF3900D0F sqlriExecThread 
0x00007FFFF3927F89 sqlrihsjn 
0x00007FFFF5B2DDE4 sqlriSectInvoke 
0x00007FFFF4F75000 sqlrr_smp_router 
0x00007FFFF4F77852 sqlrr_subagent_routerP8sqeAgent 
0x00007FFFF413BE20 sqleSubRequestRouterP8sqeAgent 
0x00007FFFF413C874 sqleProcessSubRequestP8sqeAgent 
0x00007FFFF33679AB sqeAgentRunEDUE 
0x00007FFFF3A55540 sqzEDUObjEDUDriver 
0x00007FFFF3A55497 sqlzRunEDUP 
0x00007FFFF37B7AE6 sqloEDUEntry 
 
- Was involved in either a deadlock or lock timeout. 
- The instance was running low on MON_HEAP storage (which is 
used to allocate fast writer records). 
- Activities were to be recorded in deadlock or lock timeout 
events because the database config has HISTORY specified for 
both mon_deadlock and mon_locktimeout: 
 
MON_REQ_METRICS                EXTENDED             EXTENDED 
MON_ACT_METRICS                EXTENDED             EXTENDED 
MON_OBJ_METRICS                BASE                 EXTENDED 
MON_UOW_DATA                   NONE                 NONE 
MON_LOCKTIMEOUT                NONE                 NONE 
MON_DEADLOCK                   HISTORY              HISTORY 
MON_LOCKWAIT                   HISTORY              HISTORY 
MON_LW_THRESH                  5000000              5000000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpack 2 or higher                         * 
****************************************************************
Local Fix:
db2 CONNECT TO <DATABASE> 
db2 UPDATE DB CFG USING MON_DEADLOCK WITHOUT_HIST IMMEDIATE 
db2 UPDATE DB CFG USING MON_LOCKWAIT WITHOUT_HIST IMMEDIATE
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in v10.1 Fixpack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2012
10.01.2013
10.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList