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

EXECUTION OF SQL STATEMENT WITH DBPARTITIONNUM IS NOT PARALLELIZED WHEN
USING TABLE OR LATERAL CONSTRUCT IN DPF

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
This issue only applies if you are using the database 
partitioning feature (DPF). 
 
SQL statements with an OLAP function that includes 
DBPARTITIONNUM in the partition by clause might not be 
parallelized when using the TABLE or LATERAL construct, 
executing on a single database partition in the partition group. 
For example, the following are two equivalent queries using 
LATERAL and TABLE 
 
with tmp(a,b,c) as 
(select a, 
 row_number() over (partition by dbpartitionnum(t1.b)), 
 c 
 from T1) 
select v.a, v.b, v.c 
from tmp t1, lateral(values(t1.a, t1.b, t1.c), (t1.a, t1.b, 
t1.c+1)) as v(a,b,c); 
 
with tmp(a,b,c) as 
(select a, 
 row_number() over (partition by dbpartitionnum(t1.b)), 
 c 
 from T1) 
select v.a, v.b, v.c 
from tmp t1, table(values(t1.a, t1.b, t1.c), (t1.a, t1.b, 
t1.c+1)) as v(a,b,c); 
 
If T1 is hash distributed across multiple database partitions, 
the optimizer might add a table queue to send the rows from T1 
to the coordinator to complete the operation.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using the database partitioning feature (DPF) are      * 
* affected.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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
Problem first fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.11.2012
27.09.2013
27.09.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList