DB2 FOR LUW / DB2FORLUW / 970 - DB2

SQL statement that contains two or more outer joins with the 
predicate of the first ON clause containing expressions that 
could change the null value of the left side of the LEFT outer 
join to a non-null value may return incorrect results. 
 
Example: 
 
WITH A(A1) as (values 1), 
        B(B1) as (values cast(NULL as INTEGER)), 
        C(C1) as (values 1) 
SELECT A1,B1,C1 
FROM   A LEFT JOIN (B LEFT JOIN C ON COALESCE(B1,1)=C1) ON 
A1=B1; 
 
The above statement hits this APAR because 
1. There are two outer joins. 
2. The expression in the first ON clause, COALESCE(B1,1)=C1 
could change the value of NULL of B1 to a non-null value. 
 
The correct result for the above statement is 
 
A1          B1          C1 
----------- ----------- ----------- 
          1           -           - 
 
An example of a SQL statement that does NOT hit this APAR is 
 
WITH A(A1) as (values 1), 
        B(B1) as (values cast(NULL as INTEGER)), 
        C(C1) as (values 1) 
SELECT A1,B1,C1 
FROM   A LEFT JOIN (B LEFT JOIN C ON COALESCE(B1,1)=C1) AND 
B1=C1 ON A1=B1; 
 
Even though, the COALESCE expression exists, the addition 
expression B1=C1, which return NULL if B1 is NULL, will safe 
guard this statement to not return incorrect results.

USERS AFFECTED: ALL 
 
PROBLEM DESCRIPTION: 
 
SQL statement that contains two or more outer joins with the 
predicate of the first ON clause containing expressions that 
could change the null value of the left side of the LEFT oute 
join to a non-null value may return incorrect results. 
 
Example: 
 
WITH A(A1) as (values 1), 
        B(B1) as (values cast(NULL as INTEGER)), 
        C(C1) as (values 1) 
SELECT A1,B1,C1 
FROM   A LEFT JOIN (B LEFT JOIN C ON COALESCE(B1,1)=C1) ON 
A1=B1; 
 
The above statement hits this APAR because 
1. There are two outer joins. 
2. The expression in the first ON clause, COALESCE(B1,1)=C1 
could change the value of NULL of B1 to a non-null value. 
 
The correct result for the above statement is 
 
A1          B1          C1 
----------- ----------- ----------- 
          1           -           - 
 
An example of a SQL statement that does NOT hit this APAR is 
 
WITH A(A1) as (values 1), 
        B(B1) as (values cast(NULL as INTEGER)), 
        C(C1) as (values 1) 
SELECT A1,B1,C1 
FROM   A LEFT JOIN (B LEFT JOIN C ON COALESCE(B1,1)=C1) AND 
B1=C1 ON A1=B1; 
 
Even though, the COALESCE expression exists, the addition 
expression B1=C1, which return NULL if B1 is NULL, will safe 
guard this statement to not return incorrect results. 
 
 
 
PROBLEM SUMMARY: 
 
see PROBLEM DESCRIPTION.

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 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 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
 

The complete fix for this problem first appears in DB2 UDB 
Version 9.7 FixPak 1.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.09.2009
15.12.2009
15.12.2009

9.7.