|
Problem IC74975
|
Status: Closed |
EXPLOIT INDEX ACCESS METHOD ON PREDICATE <CHARCOLUMN> = ? IN A DATABASE CREATED WITH VARCHAR2 COMPATIBILITY SETTING |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A common scenario of a predicate of the form
WHERE <charcolumn> = ?
when the parameter marker "?" is interpreted by JDBC client as
varchar.
In a database created with VARCHAR2 compatibility setting, DB2
optimizer will exploit index access method on the predicate
as an additional method. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users V9.7 FP4 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* A common scenario of a predicate of the form *
* *
* *
* *
* WHERE <charcolumn> = ? *
* *
* *
* *
* when the parameter marker "?" is interpreted by JDBC client *
* as *
* varchar. *
* *
* *
* *
* In a database created with VARCHAR2 compatibility setting, *
* DB2 *
* optimizer will exploit index access method on the predicate *
* *
* as an additional method. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP5 *
**************************************************************** |
| Local Fix: |
Upgrade to DB2 Version 9.7 Fix Pack 5 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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
|
| Solution |
First fixed in V9.7 version FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.03.2011
12.12.2011
12.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
