DB2 - Problem description
| Problem IT04780 | Status: Closed |
FETCH FIRST N ROW CLAUSE IS PUSHED DOWN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Fetch first n row clause in a federated query is pushed down.
This behaviour leads to incorrect results.
Example query:
select * from
(
select tab1.col1, tab2.col1 as vcol1
from abc123a.tab1 tab1
join schema1.tab2 tab2
ON tab2.col1 = tab1.col1
) as result1
fetch first 5 row only;
where abc123a.tab1 is a nickname
will return incorrect results because 'fetch first 5 row only'
is pushed down. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
Please use following statement to add required option to federated server definition: ALTER SERVER <FEDERATED_SERVER_NAME> OPTIONS(ADD db2_fetch_n_rows 'N') | |
| Solution | |
First fixed in DB2 10.1 Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.10.2014 17.02.2017 17.02.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|