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

INSERT FROM A CLI APPLICATION FAILS WITH CLI0112E WHEN DOUBLE DATA TYPE
COLUMN IS BOUND AS VARCHAR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
While inserting a row that has double column, insert may fail 
with CLI0112E: Error in assignment, if in CLI application double 
column was bound as 
Varchar, even though the inserted value is within the double 
range. 
 
Steps to reproduce the error: 
 
create table abcd ( col1 int, col2 int, col3 double precision); 
 
--- 
opt echo on 
opt callerror on 
sqlallocenv 1 
sqlallocconnect 1 1 
sqldriverconnect  1 0 "DSN=sample;uid=xxx;pwd=****;" -3 200 
SQL_DRIVER_NOPROMPT 
sqlallocstmt 1 1 
getmem 1 1 SQL_C_LONG 
getmem 1 2 SQL_C_LONG 
getmem 1 3 SQL_C_CHAR 500 
updatemem 1 SQL_C_LONG value 23 
updatemem 2 SQL_C_LONG value 45 
updatemem 3 SQL_C_CHAR value 307 
"-0.000000000000000000000000000000000000000000000000000000000000 
0000000000000000000000000000000000000000000000000000000000000000 
0000000000000000000000000000000000000000000000000000000000000000 
0000000000000000000000000000000000000000000000000000000000000000 
000000000000000000000000000000000000000440935284694" 
sqlprepare 1 "insert into abcd values (?,?,?)" -3 
sqlbindparameter 1 1 SQL_PARAM_INPUT SQL_C_LONG SQL_INTEGER 0 0 
1 
sqlbindparameter 1 2 SQL_PARAM_INPUT SQL_C_LONG SQL_INTEGER 0 0 
2 
sqlbindparameter 1 3 SQL_PARAM_INPUT SQL_C_CHAR SQL_VARCHAR 0 0 
3 
sqlexecute 1 
sqltransact 1 1 SQL_COMMIT 
killenv 1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI Application Users                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP5 or higher                           * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 V10.1 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.11.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList