DB2 FOR LUW / DB2FORLUW / 980 - DB2

Federated query having scalar correlated subquery predicate 
could return incorrect result. 
 
Here are some conditions which could cause this - 
 
1. It is a federated query. 
 
2. Query predicate involves scalar correlated subquery whose 
   equivalent join columns contain unique key. 
 
   A sample predicate is: 
 
   "val_or_col_1 >= (select val_or_col_2 from subQTab where 
   subQTab.c1 = outerTab.colX and subQTab.c2 = val_or_col_3)" 
 
   The subquery equivalent join columns are (c1, c2). It 
   requires primary key or unique index created on one or two 
   out of (c1, c2).

**************************************************************** 
* USERS AFFECTED:                                              * 
* Only federated queries along with the two additional         * 
* conditions which have to met (see "ERROR DESCRIPTION" for    * 
* details).                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8, Fixpack 3.                       * 
****************************************************************

If DB2COMPOPT registry is currently unset, issue "db2set 
DB2COMPOPT=0,16". Otherwise, consult DB2 service for further 
assistance.

DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

First fixed in DB2 Version 9.8, Fixpack 3.

not known / see Local fix

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

05.03.2010
08.11.2012
08.11.2012

9.8.FP3