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

DB2 MIGHT PRODUCE INCORRECT RESULTS WHEN ELIMINATING CORRELATED SCALAR
SUBQUERY

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Under rare scenarios, DB2 might produce incorrect result when 
the following conditions are true: 
1) The query contains one or more correlated scalar subqueries 
2) The scalar subquery has an aggregation function of type 
MAX/MIN 
3) The table referenced in the subquery is also joined to the 
parent of the correlation in the outer select 
4) The join predicates of the 1 and 2 are identical 
 
Eg. 
SELECT * 
FROM  tab1 d , tab2 c 
where d.c1 = c.c1 
and c.c1 = 
       ( SELECT MAX(c1) 
         FROM tab2 catg 
         WHERE catg.c1 = d.c1 );
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All which meet the conditions applied in the APAR text.      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 Fixpack 7                               * 
****************************************************************
Local-Fix:
Reduce the optimization level to 3 or below
Lösung
Upgrade to DB2 V10.5 Fixpack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2015
17.02.2017
17.02.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList