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 IC96041 Status: Closed

FOR VARCHAR COLUMN IF WE SUPPLY DATA > 32K THROUGH SQLPUTDATA IT IS
THROWING RC = SQL_ERROR AND RETURNS NO ERROR.

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
If the application is trying to insert the VARCHAR data to a 
table column through SQLPutData and execute fails with rc = -1 
and it won't return any error. It has to return the " SQL0302N 
The value of a host variable in the EXECUTE or OPEN statement is 
out of range for its corresponding use.  SQLSTATE=22001" error 
or  CLI0109E  String data right truncation. SQLSTATE=22001 
error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running the CLI application.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 version 10.1.3                               * 
****************************************************************
Local Fix:
NA
available fix packs:
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
Please upgrade to DB2 v101FP3, it will display the correct 
error.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList