|
Problem IC71600
|
Status: Closed |
CALCULATION ERROR IN CHECKS LEADING TO TOO MANY JOINS BELOW UNION ALL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A calculation problem affects UNION ALL join UNION ALL scenario.
There is a calculation error in the checks which leads to a
scenario of not detecting too many joins below the UNION.
You can workaround this problem by reducing the
MAX_JOINS_IN_UNION parameter to a set value and/or reducing the
query optimization level to 0 or 1. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V9.7 users *
****************************************************************
* PROBLEM DESCRIPTION: *
* CALCULATION ERROR IN CHECKS LEADING TO TOO MANY JOINS BELOW *
* UNION ALL *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 FP5 to avail fix for this APAR. *
**************************************************************** |
| Local Fix: |
(i) db2set DB2_UNION_OPTIMIZATION='MAX_JOINS_IN_UNION <value>'
(ii) You could also reduce the optimization level that the query
is compiled with to 0 or 1 |
| 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 |
APAR first fixed in DB2 V9.7 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.09.2010
08.12.2011
08.12.2011 |
| 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
|
 |
