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

POSSIBLE SUB-OPTIMAL QUERY PERFORMANCE WITH DB2_WORKLOAD SET TO SAP AND
CATALOG TABLE STRING COLUMN(S) USED IN COMPARISON(S)

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In SAP environments, controlled with the DB2_WORKLOAD registry 
variable set to a value of SAP, poor query performance may be 
experienced when catalog tables are used. Additional conditions 
are: 
- Database collation is IDENTITY_16BIT 
- A column from a catalog table is used in a relational operator 
for comparison 
- The catalog table column is a string column, i.e., CHAR or 
VARCHAR 
- There is a filtering index available on the other column used 
in the comparison
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All SAP environments                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In SAP environments, controlled with the                     * 
* DB2_WORKLOADregistryvariable set to a value of SAP, poor     * 
* query performance maybeexperienced when catalog tables are   * 
* used. Additionalconditionsare:- Database collation is        * 
* IDENTITY_16BIT- A column from a catalog table is used in a   * 
* relationaloperatorfor comparison- The catalog table column   * 
* is a string column, i.e., CHAR orVARCHAR- There is a         * 
* filtering index available on the other columnusedin the      * 
* comparison                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP3                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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

Solution
First fixed in DB2 V9.7 FP3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69847 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.04.2010
07.10.2010
07.10.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList