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

DB2 OPTIMIZER CAN CHOOSE A NON-OPTIMAL BLOCK INDEX TO ACCESS MDC TABLE WHEN
THE BLOCK INDEXES HAVE ONLY 1 LEVEL

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When a MDC table has more than one dimensions, and when the 
block indexes have only 1 level, the optimizer might choose a 
block index access that applies a predicate as index sargable 
rather than a more efficient block index access that applies the 
predicate as start-stop keys. 
 
For example, consider a query that references a MDC table that 
is organized by 3 columns (C1,C2,C3), and includes the predicate 
C2=1. The predicate is applied as index sargable on the index 
access of the block index on (C1, C2, C3) (refer to hereafter as 
index A) whereas it is applied as a start-stop key on the index 
access of the block index on (C2) (refer to hereafter as index 
B). The optimizer might choose an access path using index A 
rather than index B.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4                       * 
****************************************************************
Local-Fix:
Use optimization profile to force the desired index access.
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
First fixed in DB2 Version 10.5 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.03.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