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

A QUERY WITH AN OR PREDICATE MIGHT RETURN INCORRECT RESULTS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
A query might return incorrect results when the query has the 
following pattern: 
1. The query contains a subquery block, called subQ1, that 
references a base table BT1, called that quantifier Q1, and 
another subquery, called subQ2 
2. The subQ2 block references the same base table BT1. Call that 
quantifier Q2. 
3. The subQ2 block has an OR predicate, called orPrd, qualifying 
all the following conditions: 
3.a. The orPrd predicate takes the form (orPrd1 OR orPrd2 [OR 
...]).  One example could be an orPD predicate with at least two 
OR subterms denoted as orPrd1 and orPrd2. 
3.b. The orPrd predicate references column colX from Q1, and 
orPrd2 references column colX from Q2. In other words, orPrd1 is 
a correlation predicate, orPrd2 is local predicate, and their 
referenced columns derive from the same base table column. 
3.c. The orPrd1 and orPrd2 predicates are exactly matched or 
subsume each other. For example, Q1.colX=1 and Q2.colX = 1 are 
exactly matched, Q1.colX in (1,2) is subsumed by Q2.colX in 
(1,2,3). 
4. The query is compiled at optimization level 5 or above. 
 
The symptom is in the optimized statement when after either the 
orPrd1 or orPrd2 predicates are removed.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V10.5 FP3 and earlier                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.3.                             * 
****************************************************************
Local-Fix:
Reduce the query optimization level to below 5.  For example, 
issue the "db2 set current query optimization 2" command to 
reduce optimization level to 2.
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
The problem is first fixed in DB2 version 10.5.0.3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.12.2013
28.02.2014
07.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList