Latest versionsfixlist
11.1.0.6 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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC79915 Status: Closed

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

product:
DB2 CONNECT / DB2CONNCT / 950 - 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:                                              * 
* CLI based application using MSDTC                            * 
**************************************************************** 
* 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.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5, Fixpak 9                         * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5, Fixpak 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC80328 IC84191 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.11.2011
22.03.2012
22.03.2012
Problem solved at the following versions (IBM BugInfos)
9.0.,
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.