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

OPTIMIZER KEEPS UNNECESSARY COLUMNS AROUND AFTER PARTIAL GB OPERATION AND
MIGHT RESULT IN POOR PERFORMANCE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In a partitioned database environment, the DB2 optimizer can 
consider a group by (GB) alternative where the GB is partially 
performed on each database partition, accumulating partial 
results which are then re-distributed based on the grouping key 
to complete the GB. For example, if a table T is hash 
distributed across multiple database partitions based on column 
X, then for the query 
 
select a,max(b),min(c),sum(d) 
from T 
group by a 
 
the GB cannot be completed locally at each partition since the 
grouping key does not contain the hash distribution key.  As a 
result, a partial grouping result will be computed locally at 
each database partition, with the partial aggregation results 
and their source columns flowing through a table queue (TQ). 
 
If these source columns are not required beyond the partial 
result, width of the stream can be wider than is necessary which 
can significantly degrade query execution performance.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The problem only occurs in a database partitioned            * 
* environment.                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 2.                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Lösung
The problem is first fixed in DB2 version 10.1 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.10.2012
15.04.2013
15.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList