DB2 FOR LUW / DB2FORLUW / A50 - DB2

An SQL statement that includes one or more ordered column group 
OR predicates might return an incorrect result set if the DB2 
optimizer chooses a jump scan index access that applies the OR 
predicate as index range delimiting predicates for more 
efficient access. 
 
For example, the following predicate has an ordered column group 
OR predicate that defines a column group (a1, a2, a3) and an 
inclusive condition on the key values (1, 2, 3). 
 
(a1>1) or (a1=1 and a2>2) or (a1=1 and a2=2 and a3>=3) 
 
If there is an index (a1 asc, a2 asc, a3 asc), then the 
optimizer can apply the composite inclusive key for better 
filtering and minimal data read from the index.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************

You can avoid the problem by disabling jump scan using the 
JUMPSCAN option of the DB2_REDUCED_OPTIMIZATION variable: 
DB2_REDUCED_OPTIMIZATION="JUMPSCAN OFF". 
 
You can also use the REGISTRY optimization guideline element to 
set this at the application or statement level.

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 10.5.0.4.

not known / see Local fix

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

16.04.2014
08.09.2014
08.04.2015