Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06181 Status: Closed

THE OPTIMIZER CHOOSES A NON-OPTIMAL TABLESCAN TO SCAN A TABLE THAT IS BOTH
PARTITIONED BY RANGE AND MDC.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The optimizer chooses a non-optimal tablescan to scan a table 
that is both partitioned by range and mdc. 
 
The following prerequisite has to be met to hit this defect, 
 
- the query benefits from partition elimination 
- the table has a large number of overflow records 
- there is a better performing index access alternative 
 
The workaround is running REORG against the table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See SYSROUTE APARs to see where this APAR is addressed       * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.12.2014
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList