|
Problem IT39628
|
Status: Closed |
JDBC ERROR "UNRECOGNIZED JDBC TYPE: 2011 ERRORCODE=-4228, SQLSTATE=NULL " WITH JDBC
|
| product: |
DB2 CONNECT / DB2CONNCT / B50 - DB2 |
| Problem description: |
JDBC Error "Unrecognized JDBC type: 2011 ERRORCODE=-4228,
SQLSTATE=null " with JDBC Driver delivered in 11.1.4.4, 11.5.6.0
and 11.5.7.0.
Applications are getting Internal Exception:
com.ibm.db2.jcc.am.SqlException:[jcc][10271][10296][4.29.24]
Unrecognized JDBC type: 2011. ERRORCODE=-4228, SQLSTATE=null
The error is caused by inserting the value "NULL" in a column of
DBCLOB types that was defined "WITH DEFAULT NULL".
While inserting the value NULL in a column of DBCLOB types that
was defined "WITH DEFAULT NULL", Application is getting error
"Unrecognized JDBC type: 2011. ERRORCODE=-4228, SQLSTATE=null"
The issue will be fixed in upcoming db2 fix pack release
V11.5.7.1 . |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 11.1.4.4, 11.5.6.0 and 11.5.7.0 releases affected *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.8.0 or later. *
**************************************************************** |
| Local Fix: |
The issue will be fixed in upcoming db2 fix pack release
V11.5.7.1 . |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* 11.1.4.4, 11.5.6.0 and 11.5.7.0 releases affected *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.8.0 or later. *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.01.2022
07.10.2022
24.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
