home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT03730 Status: Geschlossen

DB2 MIGHT NOT OPTIMIZE EQUIVALENCE BASED PREDICATES ON COLUMN ORGANIZED
TABLES

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
Lösung
First fixed in DB2 Version 10.5 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.08.2014
20.03.2015
20.03.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList