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

OPTIMIZER MIGHT CHOOSE A SUB-OPTIMAL ACCESS FOR TABLE WITH THE SAME SINGLE
COLUMN RANGE PARTITIONING KEY AND DISTRIBUTION KEY

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Description: 
The optimizer might choose a table scan over an index access of 
a range partitioned table in a database partitioned environment 
under the following conditions: 
- the table is range partitioned and hash distributed on the 
same single column; e.g. 
    create table t1 (C1 date, ...) distribute by hash (C1) 
partition by range (C1) (starting (minvalue) ending 
('2010-12-31'), starting('2011-01-01') ending ('2011-01-31'), 
...) 
- the query contains an equality predicate on the column; e.g. 
C1='2012-01-15' 
- a partitioned index containing C1 in the key exists 
 
This problem is more likely to occur for tables with a large 
number of range partitions where the majority are empty.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* This problem is more likely to occur for tables with a large * 
* number of range partitions where the majority are empty.     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Description:                                                 * 
* The optimizer might choose a table scan over an index access * 
* of                                                           * 
* a range partitioned table in a database partitioned          * 
* environment                                                  * 
* under the following conditions:                              * 
* - the table is range partitioned and hash distributed on the * 
* same single column; e.g.                                     * 
*     create table t1 (C1 date, ...) distribute by hash (C1)   * 
* partition by range (C1) (starting (minvalue) ending          * 
* ('2010-12-31'), starting('2011-01-01') ending                * 
* ('2011-01-31'),                                              * 
* ...)                                                         * 
* - the query contains an equality predicate on the column;    * 
* e.g.                                                         * 
* C1='2012-01-15'                                              * 
* - a partitioned index containing C1 in the key exists        * 
*                                                              * 
* This problem is more likely to occur for tables with a large * 
* number of range partitions where the majority are empty.     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgraded to DB2 version 9.7 fixpack 8.                       * 
****************************************************************
Local-Fix:
You can use an optimization guideline to produce an index 
access.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Workaround
You can use an optimization guideline to produce an index 
access.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91749 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.12.2012
02.04.2013
02.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.8 FixList