|
Problem IC76575
|
Status: Closed |
A FEDERATED QUERY WITH IN PREDICATE CAN RETURN INCORRECT RESULT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A SQL query involving nicknames and IN predicate can return
incorrect result. The number of returned rows can be less than
the correct number. The query should meet the following
conditions:
1) The query has nickname involved.
2) It has IN predicate, which is internally transformed to a
join.
3) The data source of nickname is not Oracle or Sybase.
Example:
SELECT n.col1, n.col2, n.col3, n.col4, n.col5
FROM USER.NICK n
WHERE n.col1 in (select col1 from table(values ('abcd')
,('efgh')) as q1(col1))
order by 3; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customer on federated system on DB2 V9.7 and using IN *
* predicate in federated query *
****************************************************************
* PROBLEM DESCRIPTION: *
* Incorrect results are seen. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7fp5 *
**************************************************************** |
| Local Fix: |
N.A |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Issue fixed in DB2 V9.7fp5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.05.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
