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 IT20887 Status: Closed

POOR PERFORMANCE IN A FEDERATED ENVIRONMENT WHEN LOCAL PREDICATEON COLUMNS
WITH SMALL NUMBER OF DISTINCT VALUES, <=3.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Poor performance may be seen with a federated query due to a 
poor access plan selection due to the lack of statistics for the 
federated data. 
This is due to the  high2key and low2key values not be retrieved 
where the column cardinality (colcard) <=3 
 
This will only be enabled when the following DB2 Registry 
parameter is set: 
  DB2_SELECTIVITY=EXTDIST_CC1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Db2 Federated users                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1.2.2 or later.                            * 
****************************************************************
Local Fix:
Use Optimizer Profile to ensure that a good access plan is used 
for the query.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1.2.2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.06.2017
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)