home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT04780 Status: Geschlossen

FETCH FIRST N ROW CLAUSE IS PUSHED DOWN

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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')
Lösung
First fixed in DB2 10.1 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.10.2014
17.02.2017
17.02.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList