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 IT17556 Status: Geschlossen

INCORRECT RESULTS ARE POSSIBLE WHEN JOIN AGAINST CDE TABLES IS DONE AND AN
UNDOCUMENTED JOIN SUPPORT REGISTRY VARIABLE SET

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
If an undocumented join support registry variable is set and 
the plan has a left early out join with residual predicate, 
then sql might loose rows if: 
 
1.  Join between 3 or more column organized tables, using 
equality predicates 
 
2.  One of the tables has a primary key constraint that is 
referenced in the join 
 
3.  The table with the primary key constraint joins 2 or more 
other tables on the primary key constraint, but not the same 
columns; e.g. if primary key constraint is on T1 (a,b), then T1 
joins T2 on column a, and T1 joins T3 on column b.  It can 
likely occur with single column primary key as well; e.g using 
the same example, but change primary key to (a).  As long as the 
residual predicate completes the qualification of the primary 
key, then we should hit this problem. 
 
 
Example of exfmt: 
 
    3) HSJOIN: (Hash Join) 
        Cumulative Total Cost:         26173.5 
        Cumulative CPU Cost:         2.31262e+10 
        Cumulative I/O Cost:         5252 
        Cumulative Re-Total Cost:     26173.5 
        Cumulative Re-CPU Cost:     2.31262e+10 
        Cumulative Re-I/O Cost:     5252 
        Cumulative First Row Cost:     26173.5 
        Estimated Bufferpool Buffers:     4 
 
        Arguments: 
        --------- 
        EARLYOUT: (Early Out flag) 
            LEFT                             <<<<<<<<<<<<<<<< 
        SEMIJOIN: (Semi-join flag) 
            FALSE 
 
        Predicates: 
        ---------- 
        2) Predicate used in Join, 
            Comparison Operator:         Equal (=) 
            Subquery Input Required:     No 
            Filter Factor:             1 
 
            Predicate Text: 
            -------------- 
            (Q1.OBJVERS = Q3.OBJVERS) 
 
 
        3) Residual Predicate, 
<<<<<<<<<<<<<<<<<<<< 
            Comparison Operator:         Equal (=) 
            Subquery Input Required:     No 
            Filter Factor:             0.0833333 
 
            Predicate Text: 
            -------------- 
            (Q2.SID_ZLOG_MOD = Q1.SID).
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod1 Fix Pack 1                          * 
****************************************************************
Local-Fix:
UNSET AN UNDOCUMENTED JOIN SUPPORT REGISTRY VARIABLE  AND 
RESTART INSTANCE
verfügbare FixPacks:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 11.1 Mod1 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.10.2016
11.05.2017
11.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
11.1.1.1 FixList