|
Problem IC75999
|
Status: Geschlossen |
WHEN USING THE OLAP FUNCTIONS "ROW_NUMBER()" AND "OVER ()" A COMPLETE TABLE SCAN IS PERFORMED WHEN IT SHOULD NOT. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
In DB2 V9.7 FP4 and lower, when using the OLAP functions
"ROW_NUMBER()" and "OVER ()" a full table scan will be performed
when it should not.
For example, a query like "SELECT * FROM "SCHEMA.TABLE" WHERE
ROW_NUMBER() OVER () <= 1" will cause a complete table scan when
it should stop at the first row only. The problem is caused by
an issue with the optimized query rewrite. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* WHEN USING THE OLAP FUNCTIONS "ROW_NUMBER()" AND "OVER ()" A *
* COMPLETE TABLE SCAN IS PERFORMED WHEN IT SHOULD NOT. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 Fixpack 5. *
**************************************************************** |
| Local-Fix: |
NA |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 |
First Fixed in DB2 version 9.7 Fixpack 5. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 25.04.2011
09.01.2012
09.01.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
