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

Inaccurate total cost shown in query plan when intra_parallel is enabled

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The problem can occur if the optimizer chooses to 
intra-parallelize the plan. That is, the "Query Degree" shown in 
the query plan is greater than 1. 
 
This can be observed when an intra-parallelized plan is compared 
with a serial plan. The total cost of the intra-parallelized 
plan is much higher than its corresponding serial plan. 
 
For example: 
 
intra-parallelized plan: 
----------- 
    Total Cost:         1.30441e+21 
    Query Degree:       24 
 
 
serial plan: 
----------- 
    Total Cost:         1916.61 
    Query Degree:       1 
 
 
The cost difference doesn't affect query performance.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Intra-query parallelism                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
Fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.10.2014
16.07.2015
16.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList