|
Problem IC75999
|
Status: Closed |
WHEN USING THE OLAP FUNCTIONS "ROW_NUMBER()" AND "OVER ()" A COMPLETE TABLE SCAN IS PERFORMED WHEN IT SHOULD NOT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
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
|
| Solution |
First Fixed in DB2 version 9.7 Fixpack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.04.2011
09.01.2012
09.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
