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

APPLICATION MAY GET SQL1224 WITH UNICODE CLIENT IF SERVER IS DB2 FOR ZOS
AND DCS PARAMETER IS SET

Produkt:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problembeschreibung:
When DB2 registry variable DB2BIDI=YES and DCS directory is BIDI 
parameter is set with single byte codepage for example 
CCISID410,  DB2 Connect client performs layout transform on the 
input data, including the quoted strings in SQL statements 
before sending data to a DB2 for zOS database. 
If client is a unicode client or using any multibyte BIDI 
codepage and if there are quoted strings in SQL statement 
because of this defect DB2 client send incorrect SQL satement 
length. DB2 for zOS returns an error because of incorrect SQL 
satement length in the request. Client reports sqlcode SQL1224.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 7                   * 
****************************************************************
Local-Fix:
Lösung
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.02.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList