home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC77366 Status: Geschlossen

BUFFER POOL DECREASE / STMM HANG WAITING ON SPECIAL TEMP BUFFER POOL PAGE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Buffer pool decreases, often initiated by STMM, may hang for 
long periods due to special system temporary pages that are 
being held in the buffer pool.  If STMM initiated the buffer 
pool decrease, it will be hung and unable to respond to changes 
in workload or memory availability. 
 
The "special temp pages" in question are for internal system 
temporary objects that are cached for reuse until application 
termination.  A common triggering scenario is performing 
special operations such as create index or runstats on user 
temporary tables (declared or created global temporary tables). 
 
The workaround is to avoid decreasing or fix the sizes of 
buffer pools associated with system temporary tablespaces.  Note 
that although the triggering activity may be associated with 
user temporary tables in "user" temporary tablespaces, the 
internal objects are created in the "system" temporary 
tablespaces. 
 
If STMM is inoperative for long periods of time, and user 
temporary tables are commonly created on the system, this is the 
likely source of the problem. 
 
One way of determining that STMM is hung is that regular 
configuration updates cease.  A second is that the STMM logs 
stop being updated.  The STMM thread, db2stmm, regularly writes 
messages to the STMM logs (in DIAGPATH/stmmlog).  Note db2agent 
threads may still write messages to the STMM logs. 
 
A call stack of the db2stmm thread will show that it is in the 
midst of a buffer pool decrease : 
thread_wait 
getConflictComplex 
getConflict 
getConflict 
sqlbSecurePageProtection 
sqlbRemInvalidPagesFromBufferPool 
sqlbDecreaseBufferpoolSize 
sqlbResizeBufferPool 
sqlbAlterAutomaticBufferPool
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems with STMM tuning a bufferpool with an associated     * 
* tempspace                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************
Local-Fix:
Fix the sizes of buffer pools associated with system temporary 
table spaces.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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

Lösung
Problem first fixed in DB2 Version 9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC77427 IC87121 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.07.2011
27.01.2012
27.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList