DB2 - Problembeschreibung
Problem IC68135 | Status: Geschlossen |
POSSIBLE SUB-OPTIMAL QUERY PERFORMANCE WITH DB2_WORKLOAD SET TO SAP AND CATALOG TABLE STRING COLUMN(S) USED IN COMPARISON(S) | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 V9.7 FP3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69847 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.04.2010 07.10.2010 07.10.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP3 | |
Problem behoben lt. FixList in der Version | |
9.7.0.3 | |
9.7.0.3 |