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 IC84580 Status: Closed

DB2 OPTIMIZER MIGHT CHOOSE SUB-OPTIMAL INDEX-ORING ACCESS PLAN WHEN ALL
RECORDS IN THE TABLE ARE RETURNED.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If a query contains only one predicate, an IN predicate, and all 
records in the table qualify the predicate, the optimizer might 
choose an index-oring access plan as in the following example 
query and access plan: 
 
SELECT * FROM FACT WHERE YEAR IN ( 2012, 2013, 2014 ); 
 
                                 ... 
                                FETCH 
                            /-----+------\ 
                        RIDSCN     TABLE: SCHEMA1 
                          |              FACT 
                          | 
        +-----------------+-----------------+ 
      SORT              SORT              SORT 
        |                 |                 | 
      IXSCAN            IXSCAN            IXSCAN 
        |                 |                 | 
  INDEX: SCHEMA1    INDEX: SCHEMA1    INDEX: SCHEMA1 
      INDEX1            INDEX1            INDEX1 
 
If all possible values in the column YEAR are referenced in the 
values list of the IN predicate, then a table-scan access plan 
will be a better choice.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please see the Error Description section.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
06.11.2012
15.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList