DB2 FOR LUW / DB2FORLUW / 970 - DB2

The following are the necessary conditions that might cause the 
problem of "0 record(s) selected" to occur: 
 
- The DB2_COMPATIBILITY_VECTOR registry variable is set to ORA 
- A "X IN (select Y from <subquery>)" query predicate. 
- X is the CHAR type, and Y is the VARCHAR type. 
 
To verify that this problem has occurred in your query, generate 
the db2exfmt command and 
search if the optimized statement contains the following: 
 
- "(Q<num>.X >= $C3 )" 
- "(Q<num>.X <= $C2)" 
 
Also, check to see if the plan details contain: 
 
- "(ORA_VARCHAR(Q<num>.X) <= $C1 )" 
-  "(ORA_VARCHAR((Q<num>.X)>= $C0)".

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 FP9 or use the local fix as workaround.      * 
****************************************************************

Rewrite the IN predicate to the EXISTS predicate: 
 
select * 
from table1 
where pk_alansawyer in 
   (select pk_christine 
   from table2); 
 
to 
 
select * 
from table1 
where exists 
   (select 1 
   from table2 where pk_alansawyer = pk_christine);

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
 

The problem has been fixed in v9.7 FP9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95053 IC95522 
follow-up : 

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

25.03.2013
16.12.2013
16.12.2013

9.7.FP9