DB2 FOR LUW / DB2FORLUW / A10 - DB2

When a MDC table has more than one dimensions, and when the 
block indexes have only 1 level, the optimizer might choose a 
block index access that applies a predicate as index sargable 
rather than a more efficient block index access that applies the 
predicate as start-stop keys. 
 
For example, consider a query that references a MDC table that 
is organized by 3 columns (C1,C2,C3), and includes the predicate 
C2=1. The predicate is applied as index sargable on the index 
access of the block index on (C1, C2, C3) (refer to hereafter as 
index A) whereas it is applied as a start-stop key on the index 
access of the block index on (C2) (refer to hereafter as index 
B). The optimizer might choose an access path using index A 
rather than index B.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************

Use optimization profile to force the desired index access.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 4.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.03.2014
02.06.2014
02.06.2014