home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC70844 Status: Closed

INVALID CONVERSION ERROR THROWN WITH DBCHAR WITH ADDITIONAL BIND IN BIND
OUT SUPPORT IN LINUX AND WINDOWS PLATFORMS(LITTLE-ENDIA

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
Invalid conversion error thrown with dbchar with additional 
bindin bind out support for linux and Windows. 
 
 
If customer is using non-unicode data base for their application 
and trying to insert a dbclob data into a table against a 
numeric column using sqlbindparameter() function using 1202 
codepage, application hit Invalid conversion error with dbchar 
as below: 
 
> sqlbindparameter 1 3 SQL_PARAM_INPUT sql_c_dbchar sql_float 4 
0 3 
SQLBindParameter: rc = -1 (SQL_ERROR) 
SQLError: rc = 0 (SQL_SUCCESS) 
SQLError: SQLState     : 07006 
          fNativeError : -99999 
          szErrorMsg   : [IBM][CLI Driver] CLI0102E  Invalid 
conversion. SQLSTATE=07006 
          cbErrorMsg   : 62 
SQLError: rc = 100 (SQL_NO_DATA_FOUND) 
 
The problem is not there with AIX. The problem is with 1202 
codepage and non-unicode database on little indian platfrom. The 
issue is there since Cobra onwards.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Invalid conversion error thrown with dbchar with additional  * 
* bind in bind out support in Linux and Windows                * 
* platforms(little-endian machines)                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgarde to product DB2 V97fp3                                * 
****************************************************************
Local Fix:
Use unicode database or avoid using dbclob data in such cases.
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.08.2010
23.09.2010
18.03.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList