DB2 - Problem description
Problem IC63408 | Status: Closed |
THE DB2 OPTIMIZER MAY OVERESTIMATE THE COST OF A PARTITIONED INDEX ACCESS RESULTING IN A LESS-THAN-OPTIMAL QUERY ACCESS PLAN | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Partitioned indexes is a new featue in Version 9.7. The DB2 Optimizer may overestimate the cost of accessing a partitioned index which may result in the optimizer choosing a less-than-optimal query access plan for SQL statements that reference partitioned tables with partitioned indexes. It is most likely to occur for statements that don't benefit from partition elimination, but the partitioned index can apply one or more predicates which effectively access data from a small subset of the partitions. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users with partitioned indexes * **************************************************************** * PROBLEM DESCRIPTION: * * THE DB2 QUERY OPTIMIZER MAY OVERESTIMATE THE COST OF * * APARTITIONED INDEX ACCESS WHICH MAY RESULT IN * * ALESS-THAN-OPTIMAL QUERY ACCESS PLAN * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 V9.7 Fixpack 3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 V9.7 Fixpack 3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69679 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.09.2009 30.09.2010 30.09.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 | |
9.7.0.3 |