|
Problem IT08563
|
Status: Closed |
DB2 optimizer can trap when planning index jump scan on range partitioned table defined with NULLS FIRST partitioning column |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Disable jump scan by setting DB2_REDUCED_OPTIMIZATION='JUMPSCAN
OFF' |
| Solution |
Problem was first fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.04.2015
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
