DB2 - Problem description
| Problem IC91749 | Status: Closed |
OPTIMIZER MIGHT CHOOSE A SUB-OPTIMAL ACCESS FOR TABLE WITH THE SAME SINGLE COLUMN RANGE PARTITIONING KEY AND DISTRIBUTION KEY | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Description:
The optimizer might choose a table scan over an index access of
a range partitioned table in a database partitioned environment
under the following conditions:
- the table is range partitioned and hash distributed on the
same single column; e.g.
create table t1 (C1 date, ...) distribute by hash (C1)
partition by range (C1) (starting (minvalue) ending
('2010-12-31'), starting('2011-01-01') ending ('2011-01-31'),
...)
- the query contains an equality predicate on the column; e.g.
C1='2012-01-15'
- a partitioned index containing C1 in the key exists
This problem is more likely to occur for tables with a large
number of range partitions where the majority are empty. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fixpack 3. * **************************************************************** | |
| Local Fix: | |
You can use an optimization guideline to produce an index access. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Fixed in Version 10.1 Fixpack 3. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 10.10.2013 10.10.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|