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

IN DPF, WHEN UNIQUE TQ IS PRESENT IN THE PLAN AND SPECIAL INTERNAL PERF OPT
IS HAPPENING, POSSIBLE DUPLICATE VALUES RETURNED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In DPF environment when UNIQUE TQ is present in the plan and 
Special Internal Performance optimization is happening, it is 
possible to get unexpected duplicate values returned.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Mutliple Node set-up                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please, see error Description and install this Fix.          * 
****************************************************************
Local Fix:
Any one of these registry variables will work around the issue: 
 
db2set DB2_SPILL=NO_HINTS 
db2set DB2_SORT_AFTER_TQ=YES 
db2set DB2_TCG_DEFAULT_OPTIONS=set disable_pushdown on
available fix packs:
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
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
Please, see error Description and install this Fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.05.2017
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)