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

DB2 MIGHT NOT OPTIMIZE EQUIVALENCE BASED PREDICATES ON COLUMN ORGANIZED
TABLES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenario, DB2 might produce non-optimal explain plan 
due to unoptimized predicates if the following conditions are 
true: 
1) The predicates are referencing one or more column organized 
tables 
2) The predicate has a correlated reference to column from 
another table 
3) The predicate is a relational operator of type >, >=, <, <=, 
<>, etc 
4) The outer column has another equality local predicate 
 
eg. Select * 
      from t1 
      where t1.c1 = 1 and 
                 t1.c2 = (select c2 from t2 where t1.c1 <= 
t2.c1);
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using column organized table                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Manually rewrite the query and replace correlated reference with 
the constant value
Solution
First fixed in DB2 Version 10.5 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.08.2014
20.03.2015
20.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList