|
Problem IC84324
|
Status: Geschlossen |
OPTIMIZER MIGHT NOT CONSIDER A TABLESCAN OF A RANGE PARTITIONED TABLE ON THE INNER OF A NESTED LOOP JOIN |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
The query plan optimizer might not consider a table scan of a
range partitioned table on the inner of a nested loop join even
though it is not a full table scan when the pushed down join
predicates could restrict the number of partitions that are
being scanned. You might encounter this problem at optimization
class 7 and lower. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* OPTIMIZER MIGHT NOT CONSIDER A TABLESCAN OF A RANGE *
* PARTITIONED TABLE ON THE INNER OF A NESTED LOOP JOIN *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10 Fix Pack 1. *
**************************************************************** |
| Local-Fix: |
Compiling the query under optimization class 9 will enable the
optimizer to consider the table scan option. |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 Version 10 Fix Pack 1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.06.2012
10.12.2012
10.12.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
