|
Problem IC77524
|
Status: Closed |
INCORRECT RESULTS MAY BE RETURNED ON DPF WHEN QUERY CONTAINS NODENUMBER SCALAR ON EACH JOINED TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - 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: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* INCORRECT RESULTS MAY BE RETURNED ON DPF WHEN QUERY *
* CONTAINS NODENUMBER SCALAR ON EACH JOINED TABLE. *
****************************************************************
* RECOMMENDATION: *
* 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>) = <#> *
**************************************************************** |
| 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.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Fixed in DB2 V98FP4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.07.2011
05.08.2011
05.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
