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

CONTENTION ON FILELISTLATCH DUE TO TRUNCATE OF DECLARE GLOBAL TEMPOIRARY
TABLES DURING COMMIT

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If a declared global temporaray table (DGTT) with "ON COMMIT 
DELETE ROWS" specified, every subsequent commit will truncate 
the DGTT even if it has not been referenced in the UOW. 
Truncate processing needs  the fileListLatch and if there are 
many connections DGTTs, and frequent commits, contention 
develops on the fileListLatch 
 
Stack of latch contenting agent will look like so 
 
 
sqloSpinLockConflict 
getFileHandle 
sqlbSMSGetOpenInfo 
sqlbSMSTruncateObject 
sqlbTruncateObject 
sqldTableTruncate 
sqlrl_userTempDelete 
sqlrl_userTempSubActions 
sqlrl_userTempPostCleanup 
sqlrrcom 
sqlrr_commit
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* users of declared global temporary tables created with 'on   * 
* commit delete rows'                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a declared global temporaray table (DGTT) is created with * 
* the "ON COMMIT                                               * 
* DELETE ROWS" option specified, every subsequent commit will  * 
* truncate                                                     * 
* the DGTT even if it has not been referenced in the UOW.      * 
*                                                              * 
* Truncate processing needs  the fileListLatch and if there    * 
* are                                                          * 
* many connections DGTTs, and frequent commits, latch          * 
* contention                                                   * 
* develops                                                     * 
*                                                              * 
* Stack of latch contenting agent will look like so            * 
*                                                              * 
*                                                              * 
* sqloSpinLockConflict                                         * 
* getFileHandle                                                * 
* sqlbSMSGetOpenInfo                                           * 
* sqlbSMSTruncateObject                                        * 
* sqlbTruncateObject                                           * 
* sqldTableTruncate                                            * 
* sqlrl_userTempDelete                                         * 
* sqlrl_userTempSubActions                                     * 
* sqlrl_userTempPostCleanup                                    * 
* sqlrrcom                                                     * 
* sqlrr_commit                                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to Version 9.5 Fix Pack 5                            * 
****************************************************************
Local Fix:
rework application logic to use DGTTs that are not created with 
the ON COMMIT DELETE ROWS option.
available fix packs:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in Version 9.5 Fix Pack 5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64316 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.08.2009
04.01.2010
04.01.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.5 FixList