DB2 - Problem description
Problem IC80528 | Status: Closed |
OPTIMIZER MAY CHOOSE SUB-OPTIMAL ACCESS ON RANGE PARTITION TABLES EVEN WHEN THE IN PREDICATE DOES NOT FILTER ANY RECORD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
For a range partitioned table with detailed index statistics, the Optimizer might choose an in2join access plan for a query, which has only one IN predicate and that IN predicate does not filter any records i.e. filter-factor = 1. For example: SELECT * FROM FACT WHERE YEAR IN ( 2012, 2013, 2014, 2015, 2016 ); Here, all possible values of column YEAR are mentioned in the IN clause. So, a table-scan access plan will be optimal. However, the Optimizer might choose an in2join access plan graph as follows: ... NLJOIN /--------+---------\ TBSCAN FETCH | /-----+------\ TABFNC: SYSIBM IXSCAN DP-TABLE: SCHEMA1 GENROW | FACT INDEX: SCHEMA1 INDEX1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
Try collecting non-detailed index statistics. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 version 9.7 Fix Pack 6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84600 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.12.2011 14.06.2012 14.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |