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

FEDERATED QUERY HAVING SCALAR CORRELATED SUBQUERY PREDICATE COULD
RETURN INCORRECT RESULT.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Federated query having scalar correlated subquery predicate 
could return incorrect result. 
 
Here are some conditions which could cause this - 
 
1. It is a federated query. 
 
2. Query predicate involves scalar correlated subquery whose 
   equivalent join columns contain unique key. 
 
   A sample predicate is: 
 
   "val_or_col_1 >= (select val_or_col_2 from subQTab where 
   subQTab.c1 = outerTab.colX and subQTab.c2 = val_or_col_3)" 
 
   The subquery equivalent join columns are (c1, c2). It 
   requires primary key or unique index created on one or two 
   out of (c1, c2). 
 
3. Regarding the parent SELECT operator of the scalar correlated 
   subquery, the number of its join tables should be between 2 
   and 9 inclusive, and each join table should have equivalent 
   join predicate.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Only federated queries along with the two additional         * 
* conditions which have to met (see "ERROR DESCRIPTION" for    * 
* details).                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, fixpack 2.                       * 
****************************************************************
Local-Fix:
If DB2COMPOPT registry is currently unset, issue "db2set 
DB2COMPOPT=0,16". Otherwise, consult DB2 service for further 
assistance.
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
First fixed in DB2 Version 9.7, Fixpack 2.
Workaround
If DB2COMPOPT registry is currently unset, issue "db2set 
DB2COMPOPT=0,16". Otherwise, consult DB2 service for further 
assistance.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.03.2010
30.06.2010
21.01.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList