|
Problem IC96232
|
Status: Geschlossen |
QUERY ON VARCHAR2 ENABLED DATABASE DOES NOT USE INDEX SCAN |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - 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.1 fix packs 1 or 2. 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 version 10.1 fix pack 3 *
**************************************************************** |
| Local-Fix: |
Use optimization guidelines to use the appropriate index, for
example:
SELECT... /* <OPTGUIDELINES>
<IXSCAN TABLE="A" INDEX="MYINDEX"/>
</OPTGUIDELINES> */ |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 version 10.1 fix pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 25.09.2013
08.10.2013
08.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
