|
Problem IC85697
|
Status: Closed |
OPTIMIZER MIGHT CHOOSE A NON-OPTIMAL ACCESS PLAN FOR A RANGE PARTITION TABLE WITH AT LEAST ONE NON-PARTITIONED INDEX. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
This problem was introduced in DB2 Version 9.7 Fix Pack 6.
The optimizer might choose a non-optimal access plan for an SQL
statement referencing a range partitioned table with one or more
not-partitioned indexes, and containing predicates that allow
for partition elimination on that table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 For LUW Version 9.7 Fix Pack 7. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is fixed in DB2 For LUW Version 9.7 Fix Pack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.08.2012
06.11.2012
06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
