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

THE DBMS_LOB.COMPARE FUNCTION AND DBMS_LOB.READ PROCEDURE DO NOT PROCESS
CLOBS CORRECTLY IF MULTI-BYTE CHARACTERS ARE PRESENT

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The dbms_lob.compare function incorrectly expects the unit of 
measurement for the offset_1 and offset_2 parameters to be read 
in terms of the number of bytes, regardless of the type of data 
passed to the lob_1 and lob_2 parameters.  Instead, the 
dbms_lob.compare function should use number of characters as the 
unit of measurement for these parameters in order to correctly 
handle multi-byte character sets. 
 
For example, the following call to the dbms_lob.compare function 
should compare the 2nd character of each string and return -1 
because "a" is not equal to "b".  However, it return 0 because 
it is comparing the second byte of the the double-byte character 
"チ" to the second byte of the character "チ". 
db2 "values(dbms_lob.compare(clob('チa'), clob('チb'), 1, 2, 2))" 
 
Similarly, the following command should fail with SQL0138N (A 
numeric argument of a built-in string function is out of range. 
SQLSTATE=22011), but it returns -1 instead. 
db2 "values(dbms_lob.compare(clob('チa'), clob('チb'), 1, 3, 3))" 
 
The problem can only be hit when the database codepage supports 
multi-byte characters. 
 
The dbms_lob.read procedure has the same problem with the 
"offset" and "amount" parameters.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************
Local-Fix:
Lösung
The problem is first fixed in DB2 version 10.5.0.4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.03.2014
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList