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 IT02704 Status: Geschlossen

IN DPF ENVIRONMENT THE DB2 OPTIMIZER MIGHT PRODUCE A NON-OPTIMAL ACCESS
PLAN WHEN DB2_WORKLOAD=SAP

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The DB2 optimizer might produce a non-optimal access plan for 
SQL statements that are eligible for star-join optimizations 
when the DB2_WORKLOAD=SAP aggregate registry variable is set in 
a partitioned database environment. 
 
When this problem is encountered, the optimizer will produce a 
non-optimal access plan consisting of a stack of hash join 
(HSJOIN) operators with multiple large dimension tables, located 
in a single database partition, that are broadcast to complete 
the joins.  You can gather an EXPLAIN of the affected queries to 
confirm this pattern of operations in the access plan.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on DB2 V10.1 Fixpak 4 and below                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpak 5                                * 
****************************************************************
Local-Fix:
You can try any of the following options for the tables located 
in a single database partition: 
 
1) Redistribute the table across multiple partitions, located in 
the same partition group as the fact table, using the join 
columns as the distribution key.  This can also be accomplished 
as a temporary fix by creating a MQT as (select * from table) 
that is located in the same partition group as the fact table 
 
2) Create a replicated MQT of the table, locating the MQT in the 
same partition group as the fact table
Lösung
First fixed in DB2 v10.1 Fixpak 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.06.2014
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList