DB2 - Problembeschreibung
| Problem IC84580 | Status: Geschlossen |
DB2 OPTIMIZER MIGHT CHOOSE SUB-OPTIMAL INDEX-ORING ACCESS PLAN WHEN ALL RECORDS IN THE TABLE ARE RETURNED. | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
If a query contains only one predicate, an IN predicate, and all
records in the table qualify the predicate, the optimizer might
choose an index-oring access plan as in the following example
query and access plan:
SELECT * FROM FACT WHERE YEAR IN ( 2012, 2013, 2014 );
...
FETCH
/-----+------\
RIDSCN TABLE: SCHEMA1
| FACT
|
+-----------------+-----------------+
SORT SORT SORT
| | |
IXSCAN IXSCAN IXSCAN
| | |
INDEX: SCHEMA1 INDEX: SCHEMA1 INDEX: SCHEMA1
INDEX1 INDEX1 INDEX1
If all possible values in the column YEAR are referenced in the
values list of the IN predicate, then a table-scan access plan
will be a better choice. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * Please see the Error Description section. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 Fix Pack 1. * **************************************************************** | |
| Local-Fix: | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Lösung | |
Upgrade to DB2 version 10.1 Fix Pack 1. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.06.2012 06.11.2012 15.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|