|
Problem IC80526
|
Status: Closed |
COMPARING TIMESTAMP TYPE COLUMN WITH CHAR/VARCHAR TYPE HOST VARIABLE MAY GET SUBOPTIMAL QUERY PLAN IN V97 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When query statement includes a predicate comparing a TIMESTAMP
base table column with a host variable of type CHAR or VARCHAR,
a TIMESTAMP casting function may be added out of the host
variable, and that may cause the predicate to be not optimized
and evaluated very efficiently. That TIMESTAMP casting function
can be found in "Optimized Statement" section of db2exfmt
generated query plan. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fixpack 6 or later. *
**************************************************************** |
| Local Fix: |
Change host variable type to TIMESTAMP. |
| available fix packs: |
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 |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84288
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.12.2011
14.06.2012
14.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
