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

GRAPHIC KEYWORD GETS RESET AFTER ENLISTING IN MSDTC. THIS CAN CAUSE SQL
SERVER TO FAIL WITH -332 ERROR.

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
When using Microsoft SQL Server to initiate an Update statement 
against DB2 for z/OS using DB2 Connect and the IBM OLE DB 
provider, the statement can fail with the following error 
message: 
 
[IBM][CLI Driver][DB2] SQL0332N  Character conversion from the 
source code page "1208" to the target code page "65534" is not 
supported.  SQLSTATE=57017 
 
The DB2 provider will by default assume that GRAPHIC data types 
are supported.  SQL Server in this case will append a G' to the 
front of the literal in the SQL statement causing the database 
server to fail with the SQL0332N error message. 
 
The DB2 client has a db2cli.ini keyword called GRAPHIC=0 that 
should prevent SQL Server from appending the G' to the front of 
the literal.  However once a distributed transaction is made 
with MSDTC, the DB2 client provider resets the GRAPHIC keyword 
back to 1 which then causes the SQL0332N error again. 
 
This APAR is used to ensure that even after the transaction is 
enlisted with MSDTC, that the DB2 client driver will not reset 
the GRAPHIC keyword back to 1. 
 
The GRAPHIC=0 keyword will still need to be used however.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Using Microsoft SQL Server to initiate an Update statement   * 
* against DB2 for z/OS using DB2 Connect and the IBM OLE DB    * 
* provider.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product v9.7.6                                    * 
****************************************************************
Local-Fix:
n/a
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.12.2011
14.06.2012
14.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList