|
Problem IC96232
|
Status: Closed |
QUERY ON VARCHAR2 ENABLED DATABASE DOES NOT USE INDEX SCAN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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> */ |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 version 10.1 fix pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
