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 IT24687 Status: Closed

QUERIES USING THE SAME UNNEST IN DIFFERENT PARTS OF THE PLAN COULD RETURN
WRONG RESULTS FOR SOME COLUMNS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
QUERIES USING THE SAME UNNEST IN DIFFERENT PARTS OF THE PLAN 
COULD RETURN WRONG RESULTS FOR SOME COLUMNS 
 
example of the query is below and UNNEST(accounts_in) will be 
referenced in two different lolepops in the plan. 
 
with TAB1 as ( select T.id , T.ACCT from UNNEST(accounts_in) 
WITH ORDINALITY as T(ACCT, id) ) , 
       TAB2 as ( select distinct ACCT AS DACCT from TAB1 ) 
 
select * from TAB1 LEFT OUTER JOIN TAB2 ON TAB1.ACCT = 
TAB2.DACCT 
 
One of the columns (ACCT or DACCT) could return a wrong value.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Fixpack 3 Mod 2 or higher                * 
****************************************************************
Local Fix:
N/A
Solution
First fixed in Db2 11.1 Fixpack 3 Mod 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2018
07.08.2018
07.08.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)