|
Problem IC67304
|
Status: Closed |
POSSIBLE WRONG RESULTS: COALESCE ON FULL OUTER JOIN OF 2 SUBSELE CTS THAT OUTPUT >= 1 NOT-NULL COLUMNS AND A LITERAL OR GROUP BY |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Incorrect results may be returned if following conditions are
satisfied:
1) FULL OUTER JOIN (FOJ) used in query
2) COALESCE function used on two or more columns after
application of FOJ
3) The first parameter column to COALESCE sources from a
not-nullable base-table column
4) The inputs to FOJ are nested subselects
5) One or both nested subselects either:
5.a) Output a constant literal as a column, which is used after
application of FOJ, OR
5.b) Contain a GROUP BY clause where the output columns of the
subselect are columns, literals, column functions or
deterministic functions only |
| Problem Summary: |
USERS AFFECTED: All
PROBLEM DESCRIPTION:
see ERROR DESCRIPTION
PROBLEM SUMMARY:
see ERROR DESCRIPTION |
| Local Fix: |
Rewrite any problematic queries to preclude any of the
conditions above, e.g., use a CASE expression instead of
COALESCE |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The complete fix for this problem first appears in DB2 UDB
Version 9.5 FixPak 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68418 IC68419 IC68420 IC68421
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.03.2010
14.05.2010
14.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
