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

INSERT OF A UCS-2 LOB IF SPLIT BETWEEN BUFFERS ON A SURROGATE CHARACTER
COULD INSERT BAD DATA FOR THIS SURROGATE CHARACTER

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When inserting LOB data into the database and LOB data is in 
UCS-2 codepage and target codepage of the column is UTF-8, then 
the following could happen: 
If data is split across multiple communication buffers, and we 
split UCS-2 surrogate character (ex: xD840DD0C) across 2 buffers 
, 
then during conversion from UCS-2 to UTF-8 we could insert bad 
data into the database. 
example: split is as such :  one buffer ending with "D840" and 
next one starting with "DD0C" , then 
we could insert: EDA180 EDB48C instead of expected xF0A0848C
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* UCS-2 LOBS                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install This fix                                             * 
****************************************************************
Local-Fix:
N/A
Lösung
See Error Description
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.07.2015
19.01.2016
19.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList