|
Problem IC80529
|
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 / 970 - 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: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 Fix Pack 6 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 version 9.7 Fix Pack 6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84580
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 20.12.2011
14.06.2012
15.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP6
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.6
|
 |
