DB2 - Problem description
Problem IC69847 | 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 / 980 - 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 * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.8 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
Solution | |
First fixed in DB2 Version 9.8 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.07.2010 02.08.2011 02.08.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.4 |