home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68119 Status: Geschlossen

Crash for query that contains like in a mixed/EUC codepage database.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
This problem is first fixed in version 9.7 fixpack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2010
24.09.2010
24.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList