DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 optimizer can trap when it plans an index jump scan on a 
range partitioned table, and when all of the following 
conditions are present: 
 
- At least one of the partitioning columns of the range 
partitioned table is defined with NULLS FIRST. 
- The partitioning columns are a prefix of the index columns. 
- The gap column in the jump scan is not referenced in the SQL 
statement that is being compiled. 
 
The stack trace-back contains the following: 
 
sqlno_find_index_global_order_prefix 
sqlno_prop_iscan_prep 
sqlno_prop_iscan 
ISCAN

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

Disable jump scan by setting DB2_REDUCED_OPTIMIZATION='JUMPSCAN 
OFF'

Problem was first fixed in DB2 Version 10.1 Fix Pack 5.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.04.2015
13.07.2015
13.07.2015