home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96264 Status: Closed

FED:FEDERATED QUERY WITH A LARGE AMOUNT OF COLUMNS COULD EXPERIENCE LONG
TIME COMPILATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The compilation time for federated query that involves 
nicknames and a large amount of columns could be very long. It 
results from some inefficient way to handle  columns in 
compilation. It can be hit with the following conditions: 
1) there is at least one nickname involved in the query 
2) there are a large amount of columns involved in the query 
even if the columns are from local table of the queries.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platforms, all relational data sources                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v101fp3                                           * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
v101fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.09.2013
31.10.2013
31.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList