home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC87146 Status: Closed

HANG DURING BUFFERPOOL FLUSH WHEN STMM IS ALTERING A BUFFERPOOL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This is a timing issue that can happen when the following 
conditions are true: 
 
1) STMM: 
- altering a buffer pool 
- holding SQLO_LT_SQLB_BufferPool__prevBPDCachingLatch 
- waiting on page cleaner waitpost 
 
Stack trace: 
sqloWaitEDUWaitPost 
sqlbPauseCleanerGroup 
sqlbFinalizeRTBPState 
sqlbAlterBufferPoolAct 
 
2) Page cleaner: 
- waiting on an exclusive latch for page P1 
 
Stack trace: 
sqloltch_notrack 
sqlbClnrAsyncWriteSetup 
sqloDispatchNBlocks 
sqloLioReadWriteNBlocks 
sqlbClnrDispatchSomeAIO 
sqlbClnrWriteSerializeIOList 
sqlbClnrWritePages 
sqlbClnrFindWork 
 
3) Any EDU driving a flush of the dirty list by writing a log 
record, e.g. 
 
a) Index manager adding an index key: 
- holding an exclusive latch on page P2 
- holding SQLO_LT_SQLP_DBCB__add_logspace_sem 
- waiting on SQLO_LT_SQLB_BufferPool__prevBPDCachingLatch 
 
Stack trace: 
sqlbFlushForDLSubset 
sqlbFlush 
sqlbflshConditional 
sqlpgResSpace 
sqlpWriteLR 
sqliakn 
sqlischa 
sqlischa 
 
b) At the same time, another Index manager EDU holding page P1, 
e.g. during runstats processing: 
- holding a shared latch on page P1 
- waiting on a shared latch on page P2 
 
Stack trace: 
sqlbfix 
sqlifix 
sqliFixPageWithChildPtr 
sqlischs 
sqlistat 
sqldIndexStats 
sqlrLocalRunstats 
sqlrrsta 
sqlrr_runstats_DA
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 8.                       * 
****************************************************************
Local Fix:
The workaround is to disable STMM.
available fix packs:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix pack 8.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC87456 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.10.2012
01.04.2013
01.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList