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

Latch contention issue in XML pathID cache could cause performance issues.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Performance could have been impacted if there are many 
activities on XML pathID cache.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix pack 2                                        * 
****************************************************************
Local Fix:
Introduce hash table for XML pathID cache to reduce the latch 
contention. 
 
db2set DB2_COMPILER_XML_OVERRIDES=00000000000000000000n 
where n can be 1 to 9 
db2stop force 
db2start 
 
The number n represents the power of 2 size of the hash table 
cache (as an example, if n = 7, it will have 128 hash buckets 
for the XML pathID cache).
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 Db2 V10.1 fp 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
20.12.2012
20.12.2012
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