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 IC65751 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - 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 patterntocompare has prefixed   * 
* characters followed by wildcard such asthis example:select   * 
* columns from table where pattern like "abc%"2) The data is   * 
* in a mixed or EUC codepage3) The pattern "abc%" has a length * 
* that is greater than thecolumn data that is being            * 
* scanned.Then there exists the possibility that the           * 
* comparison may doaninvalid memory access that will crash the * 
* instance. In verytinyopportunity, a wrong result might       * 
* return.If a stack traceback is generated, the function at    * 
* the topofthe stack will be an OS memory compare function     * 
* (differsdepending on platform, eg. intel_fast_memcmp on      * 
* Intelplatform)with sqlv_mixd_short_search() below it.        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 9.5 fix pack 6 or later.                   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This problem is first fixed in version 9.5 fix pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68119 IC68120 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.01.2010
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version