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

QUERY ON VARCHAR2 ENABLED DATABASE DOES NOT USE INDEX SCAN

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
A query that may have been perfoming well in a prior release of 
DB2 but may stop choosing an index after upgrading to DB2 
version 10.5.  This can happen on a VARCHAR2 
enabled database when the query includes basic predicates 
involving VARCHAR columns.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4                       * 
****************************************************************
Local-Fix:
Use optimization guidelines to use the appropriate index, for 
example: 
 
SELECT... /* <OPTGUIDELINES> 
           <IXSCAN TABLE="A" INDEX="MYINDEX"/> 
     </OPTGUIDELINES> */
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 Cancun Release 10.5.0.4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.09.2013
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList