|
Problem IC68119
|
Status: Closed |
Crash for query that contains like in a mixed/EUC codepage database. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the following conditions are met:
1) A query contains a "like" comparison, where the pattern to
compare has prefixed characters followed by wildcard such as
this example:
select columns from table where pattern like "abc%"
2) The data is in a mixed or EUC codepage
3) The pattern "abc%" has a length that is greater than the
column data that is being scanned.
Then there exists the possibility that the comparison may do an
invalid memory access that will crash the instance. In very tiny
opportunity, a wrong result might return.
If a stack traceback is generated, the function at the top of
the stack will be an OS memory compare function (differs
depending on platform, eg. intel_fast_memcmp on Intel platform)
with sqlv_mixd_short_search() below it. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the following conditions are met: *
* *
* 1) A query contains a "like" comparison, where the pattern *
* to compare has prefixed characters followed by wildcard such *
* as this example: *
* select columns from table where pattern like "abc%" *
* *
* 2) The data is in a mixed or EUC codepage *
* *
* 3) The pattern "abc%" has a length that is greater than the *
* column data that is being scanned. *
* *
* Then there exists the possibility that the comparison may do *
* an invalid memory access that will crash the instance. In *
* very tiny opportunity, a wrong result might return. *
* *
* If a stack traceback is generated, the function at the top *
* of the stack will be an OS memory compare function (differs *
* depending on platform, eg. intel_fast_memcmp on Intel *
* platform) with sqlv_mixd_short_search() below it. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97fp3 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is first fixed in version 9.7 fixpack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2010
24.09.2010
24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
