|
Problem IT09321
|
Status: Geschlossen |
DB2 optimizer can trap when planning index jump scan on range partitioned table defined with NULLS FIRST partitioning column |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 7. *
**************************************************************** |
| Local-Fix: |
Disable jump scan by setting DB2_REDUCED_OPTIMIZATION='JUMPSCAN
OFF' |
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 08.06.2015
20.01.2016
20.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
