|
Problem IT30258
|
Status: Closed |
JDBC ERROR "UNRECOGNIZED JDBC TYPE:-15 ERRORCODE=-4228, SQLSTATE=NULL "
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem description: |
Java T4 Applications are getting Internal Exception:
com.ibm.db2.jcc.am.SqlException: [jcc][10271][10296][4.26.14]
Unrecognized JDBC type: -15. ERRORCODE=-4228, SQLSTATE=null with
the new JDBC Drivers 4.25.1301 ( v11.1m4fp4iFix) and 4.26.14. (
v11.5 GA)
The error is caused by inserting the value "NULL" in a column of
GRAPHIC and VARGRAPHIC types that was defined "WITH DEFAULT
NULL"
The issue will be fixed in v11.1m4fp5 and v11.5fp1 or later |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* The issue will be fixed in v11.1m4fp5 and v11.5fp1 or later *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* 2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* The issue will be fixed in v11.1m4fp5 and v11.5fp1 or later *
**************************************************************** |
| Comment |
Java T4 Applications throwing Exception:
com.ibm.db2.jcc.am.SqlException: [jcc][10271][10296][4.26.14]
Unrecognized JDBC type: -15. ERRORCODE=-4228, SQLSTATE=null with
the new JDBC Drivers 4.25.1301 ( v11.1m4fp4iFix) and 4.26.14. (
v11.5 GA)
The error is caused by inserting the value "NULL" in a column of
GRAPHIC and VARGRAPHIC types that was defined "WITH DEFAULT
NULL" |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.09.2019
23.02.2020
23.02.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
