home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT04924 Status: Closed

WHEN INTRA_PARALLEL ENABLED, SQL STATEMENT WITH IN PREDICATE MIGHT RETURN
INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An incorrect result set might be produced when INTRA_PARALLEL is 
enabled for a SQL statement if all of the following conditions 
are met: 
(a) the statement contains an IN predicate referencing a numeric 
column type that is not an integer 
(b) the values list of the IN predicate contains integer values 
(c) the optimizer produces an access plan with a MSJOIN to apply 
the IN predicate as a join 
(d) the query degree of the access plan is > 1 
 
For example, if the column DECCOL is of type decimal, then the 
following IN predicate satisfies conditions (a) and (b): 
DECCOL IN (1,2,3) 
 
You can collect an EXPLAIN of the statement to confirm if a 
MSJOIN operation is performed and the query degree of the access 
plan is a value > 1.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.5.                             * 
****************************************************************
Local Fix:
You can attempt to avoid the MSJOIN operation by using an 
optimization guideline to request a different join alternative, 
such as NLJOIN or HSJOIN.
Solution
The problem is first fixed in DB2 version 10.5.0.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.10.2014
09.04.2015
09.04.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList