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

BUGCHECKEXCEPTION: BUG CHECK EXCEPTION THROWN DUE TO AN INTERNAL JCC ERROR
SEVERITY CODE 8, ERRORCODE=-4228

product:
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2
Problem description:
The following exception is thrown by the IBM Data Server Driver 
for JDBC and SQLJ (also called JCC driver) when a prepared 
statement (PreparedStatement object) is executed: 
 
com.ibm.db2.jcc.am.BugCheckException: [...] Bug check exception 
thrown due to an internal JCC error.  Please contact support. 
Message text: Error happened on server. Severity code 8. No 
exception code returned from server. ERRORCODE=-4228, 
SQLSTATE=null 
 
The scenario that leads to the exception is: 
 
1. Client reroute is enabled by configuring client affinities or 
setting the JCC driver property enableSyspleWLB=true. 
2. A connection undergoes client reroute - either when the 
connection is first made or or at some point later when the 
connection is used. 
3. The application executes a prepared statement 
(PreparedStatement object) that has a parameter whose JDBC data 
type is any of BLOB, CLOB, LONGVARCHAR, LONGVARBINARY, BINARY or 
LONGVARGRAPHIC.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of IBM Data Server Driver for JDBC and SQLJ        * 
* shipped with DB2 10.1 releases earlier than DB2 10.1 Fixpack * 
* 5                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer error description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fixpack 5                                * 
****************************************************************
Local Fix:
Catching and ignoring the exception and executing the prepared 
statement (PreparedStatement object) again should work.
Solution
Upgrade to DB2 10.1 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.03.2014
22.07.2015
22.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