home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC80899 Status: Closed

COALESCE EXPRESSION IN THE OUTER JOIN OPERATOR (+) MAY RETURN INCORRECT
RESULTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may return incorrect result when DB2_COMPATIBILITY_VECTOR is 
set to support the OUTER JOIN (+) syntax, and all the conditions 
below are met: 
 
1. WHERE clause contains a predicate with COALESCE function. 
2. The COALESCE function contains a column from the table used 
in the (+) operator. 
3. The column in 2) is defined NOT NULL. 
4. Another predicate AND to the predicate with COALESCE function 
in (1). 
 
For example: 
CREATE TABLE T1(C1 INTEGER, C2 INTEGER NOT NULL); 
CREATE TABLE T2(C1 INTEGER); 
 
INSERT INTO T1 VALUES (1,1); 
INSERT INTO T2 VALUES 1,2; 
 
SELECT T1.C1,T2.C1 FROM T1,T2 WHERE T1.C1 (+) = T2.C1 AND 
COALESCE(T1.C2,1) = 1 AND T2.C1=2; 
 
The correct result should return 1 row. 
 
T1.C1        T2.C1 
-----------  ----------- 
          -            2 
 
This problem is fixed in DB2 Version 9.7 Fix Pack 6.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 6.                       * 
****************************************************************
Local Fix:
There are two possible workarounds, 
1) Use the ANSI syntax of the OUTER JOIN 
 
The example above can be written as 
SELECT T1.C1,T2.C1 FROM T1 RIGHT OUTER JOIN T2 ON T1.C1=T2.C1 
WHERE COALESCE(T1.C2,1) = 1 AND T2.C1=2; 
 
2) Separate the COALESCE predicate into a subselect after the 
OUTER JOIN (+) operator predicate 
 
The example above can be written as 
SELECT T1C1, T2C1 
FROM (SELECT T1.C1 as T1C1, T1.C2 as T1C2, T2.C1 as T2C1 FROM 
T1,T2 WHERE T1.C1(+) = T2.C1) AS Q 
WHERE COALESCE(T1C2, 1) = 1 AND T2C1=2;
available fix packs:
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
Upgrade to DB2 version 9.7 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84320 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.01.2012
30.10.2012
25.09.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList