|
Problem IC89730
|
Status: Closed |
POSSIBLE PERFORMANCE REGRESSION FROM SCALAR SUBQUERY PUSH DOWN INTO OUTER JOIN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A SQL statement containing a predicate with a scalar subquery
used in the context of >=, >, <=, <, !=, may NOT be pushed down
below Outer Join operations. If the predicate could filter high
number of rows from the table(s) from the outer joins, this
could potentially degrade the performance of the statement.
This problem effects when upgrading from DB2 version 9.1 Fix
Pack 7 or 8, version 9.5 Fix Pack 4 or 5, version 9.7 GA or Fix
Pack 1 to version 9.7 Fix Pack 2 to 7. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
Upgrade to DB2 version 10.1 Fix Pack 3 |
| available fix packs: |
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
|
| Solution |
This problem has been resolved in DB2 version 10.1 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.01.2013
02.10.2013
02.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
