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

VIRTUAL DATABASE PARTITIONING IS NOT USED WHEN EVALUATING PARTITIONING
USING THE ADVISOR OR EXPLAIN IN DPF ENVIRONMENTS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The virtual database partitioning specified in the 
ADVISE_PARTITION table may not be considered when using the 
EVALUATE PARTITIONINGS explain mode or the design advisor 
partitioning mode.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF mode on all platforms                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The virtual database partitioning specified in the           * 
* ADVISE_PARTITION table may not be considered when using the  * 
* EVALUATE PARTITIONINGS explain mode or the design advisor    * 
* partitioning mode. This may cause the recommended            * 
* partitioning to be inaccurate.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2LUW version 10.5 Fix Pack 4                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem is fixed in DB2LUW version 10.5 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.05.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList