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

WRONG RESULTS MAY OCCUR IF THE QUERY CONTAINS EXISTENTIAL SUBQUE RIES AND A
CORRELATED UNION ALL CONSUMED IN THE SAME SUBSELECT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Wrong results have been noted on all version of DB2 if the 
following conditions are true: 
 
1. There are two or more existential subqueries present in the 
query. 
2. There is a UNION ALL with the following characterstics: 
   a. One arm of the UNION ALL has less number of tables as 
compared to other arm(s) 
   b. The UNION ALL is correlated to the subqueries. 
3. The existential subqueries are consumed in the same subselect 
that consumes the Union ALL
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using subqueries and union all views in            * 
* theirqueries                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Wrong results have been noted on all version of DB2 if       * 
* thefollowing conditions are true:1. There are two or more    * 
* existential subqueries presentinthe query.2. There is a      * 
* UNION ALL with the following characterstics:a. One arm of    * 
* the UNION ALL has less number of tables ascompared to other  * 
* arm(s)b. The UNION ALL is correlated to the subqueries.3.    * 
* The existential subqueries are consumed in the samesubselect * 
* that consumes the Union All                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to Version 9.7 Fix Pack 2                             * 
****************************************************************
Local-Fix:
Change the value of CURRENT QUERY OPTIMIZATION special register 
to 0 
SET CURRENT QUERY OPTIMIZATION 0;
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.12.2009
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList