|
Problem IC68351
|
Status: Closed |
INCORRECT RESULTS MAY BE RETURNED ON DPF WHEN QUERY CONTAINS NODENUMBER SCALAR ON EACH JOINED TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Incorrect results may be returned on DPF when the query
uses outer join and contains NODENUMBER scalar in each joined
table.
EX:
SELECT ...
FROM A LEFT JOIN B
ON A.<column> = B.<column>
WHERE NODENUMBER(A.<column>) = <#>
AND NODENUMBER(B.<column>) = <#> |
| Problem Summary: |
INCORRECT RESULTS MAY BE RETURNED ON DPF WHEN QUERY
CONTAINS NODENUMBER SCALAR ON EACH JOINED TABLE. |
| Local Fix: |
Run the query using NODENUMBER scalar only on the first table of
the outer join.
SELECT ...
FROM A LEFT JOIN B
ON A.<column> = B.<column>
WHERE NODENUMBER(A.<column>) = <#> |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
Fixed in DB2 V97FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.05.2010
29.09.2010
29.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
