|
Problem IT24688
|
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 / A50 - DB2 |
| Problem description: |
Simple Reproduction:
db2 "CREATE TYPE accounts AS CHARACTER(9) ARRAY[100]"
db2 "create variable accounts_in accounts"
db2 "set accounts_in = ARRAY['045HE2373']"
db2 "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"
ID ACCT DACCT
----------- --------- ---------
1 - 045HE2373
1 record(s) selected.
We can see that value of ACCT column is reported as Null which
is not correct. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* See Error Description *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 10.5 Fp10 *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT24687
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.04.2018
11.07.2018
12.07.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
