|
Problem IC84191
|
Status: Closed |
GRAPHIC KEYWORD GETS RESET AFTER ENLISTING IN MSDTC. THIS CAN CAUSE SQL SERVER TO FAIL WITH -332 ERROR. |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows users, using MSDTC *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1, Fixpak 1 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1, Fixpak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
