DB2 - Problem description
Problem IT02254 | Status: Closed |
DB2 FEDERATION: UNION OF SELECT ON NICKNAMES WITH FETCH FIRST N ROW CLAUSE COULD RETURN INCORRECT RESULTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
In a federated scenario with 2 DB2 LUW databases a UNION of SELECT on nicknames with fetch first n row clause could return incorrect results. The problem could be hit when following conditions are met: 1) There is a UNION in the query 2) The UNION has two or more SELECT branches which queries data from nicknames of one same server. 3) One of the SELECT has Fetch First N Rows Only clause The fetch first n rows clause could be missing during query processing resulting in incorrect result. E.g. (SELECT * from nickname1 order by c1 fetch first 10 rows only) UNION (SELECT * from nickname2 order by c1 fetch first 10 rows only) With this problem, the result of the query could be larger than 20 records. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5. * **************************************************************** | |
Local Fix: | |
Solution | |
First fixed in DB2 Version 10.1 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.06.2014 14.07.2015 14.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |