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 IC95053 Status: Closed

THE QUERY STATEMENT WITH A SUBQUERY PREDICATE MIGHT NOT RETURN ROWS AFTER
ENABLING DB2_COMPATIBILITY_VECTOR=ORA

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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)".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.3.                             * 
****************************************************************
Local Fix:
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);
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is first fixed in DB2 version 10.1.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList