A fix is available
APAR status
Closed as program error.
Error description
New release of the IBM DB2 Driver for JDBC and SQLJ (release 3.58) providing various enhancehment and service updates. ADDITIONAL SYMPTOMS for the Type-2 z/OS Connectivity: ===================================================== Possible SIGSEGV (ABENDS0C4) may occur during JVM shutdown/termination...running JDK 1.5 SR11(or higher) - Applications may abend with U4087 or loop or report high CPU Example traceback for the failing / looping thread follows __zerro +00000AEA CELHV003 HLE7760 Exception __zerros +000001D6 CELHV003 HLE7760 Call CEEVROND +000011EA CEEPLPKA Call CEEHDSP +00000D2C CEEPLPKA UK51026 Call CEEHRNUH +00000096 CEEPLPKA HLE7760 Call __zerro +00000AEA CELHV003 HLE7760 Exception __zerros +000001D6 CELHV003 HLE7760 Call CEEVROND +000011EA CEEPLPKA Call CEEHDSP +00000D2C CEEPLPKA UK51026 Call CEEHRNUH +00000096 CEEPLPKA HLE7760 Call sigaction +00000352 CELHV003 HLE7760 Exception real_sigaction +0000000C *PATHNAM j100122 Call jsig_primary_signal +00000210 *PATHNAM j100122 Call J9VMDllMain +00000452 *PATHNAM j100122 Call runJ9VMDllMain +00000108 *PATHNAM j100122 Call pool_do +00000146 *PATHNAM j100122 Call freeJavaVM +00000564 *PATHNAM j100122 Call protectedDestroyJavaVM +000004DC *PATHNAM j100122 Call j9sig_protect +000002CA *PATHNAM j100122 Call DestroyJavaVM +00000204 *PATHNAM j100122 Call DestroyJavaVM +00000012 *PATHNAM j100122 Call sjcsdes +000000FA DFHSJCSL Call dfhsjcsl -7FFFFF42 DFHSJCSL Call @@FECB -29F99486 Call CEEVROND +000011EA CEEPLPKA Call CEEBPCAS +00000CDE CEEPIPI HLE7760 Call
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: ALL Users of the * * IBM DB2 Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM DB2 Driver for JDBC and SQLJ * * version 3.58.127 is provided by this * * APAR ( JCCV358127 ) * * * * This APAR is applicable to * * IBM DB2 Driver for JDBC and SQLJ * * for both DB2 z/OS V9 and the * * alternate supplemental driver * * for DB2 z/OS V8. * * ( JCCZOSDB2V8, JCCZOSDB2V9 ) * * * * This APAR delivers a service bundling * * to release 3.58 of the IBM DB2 Driver * * for JDBC and SQLJ providing an * * accumulation of defect fixes and * * enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: ____________________________________________________________ All Connectivities: An ArrayIndexOutOfBoundException may be thrown for a heterogeneous batch in static SQLJ if the batched statements have different numbers of parameter markers. This problem has been fixed. (139796) ____________________________________________________________ All Connectivities: Previously, setObject with value null for static path would fail with SQLException "Invalid data conversion: Parameter instance null is invalid for the requested conversion". Now JCC allows setObject with null for static path if it's not for zOS stored procedure. (140483) ____________________________________________________________ Type-4 Connectivity: Under a sysplexWLB environment, when trying to get an initial connection by calling the DB2ConnectionPoolDataSource.getConnection() method, a java.lang.NullPointerException might be thrown after multiple reoccurring SQLCODE4499 (-4499) errors because some of the sysplex members were unavailable. This has been fixed. (137437) ____________________________________________________________ Type-4 Connectivity: Under a sysplexWLB environment with the sslConnection property enabled, the driver fails to failover to other sysplex members if the current member goes down in the middle of a transaction. This has been fixed. (138627) ____________________________________________________________ Type-4 Connectivity: Driver throws an SQLException with SQLCODE4499 (-4499) with the message "The DDM object is not supported. Unsupported DDM object code point: 0x220a" while inserting a BigDecimal via the gateway going to DB2 for iSeries. This problem has been fixed. (138861) ____________________________________________________________ Type-4 Connectivity: Under sysplexWLB environment for DB2 pureScale server, when a member is stopped in quiesce mode and then restarted, applications might not be able to connect to that member and an SQLException with SQLCODE4499 (-4499) will be thrown repeatedly. This has been fixed. (138430) ____________________________________________________________ Type-4 Connectivity: Under sysplexWLB environment for DB2 pureScale server, applications can not make any connection to a member that has 100% workload. This problem has been fixed. (138519) ____________________________________________________________ Type-4 Connectivity: Under sysplexWLB environment, an SQLException with SQLCODE204 (-204) will be thrown while executing the first SQL if there is a special register property that is set in the datasource and a rollback is the first method to be called on the connection before any SQL statement is executed. This has been fixed. (138991) ____________________________________________________________ Type-4 Connectivity: An XAER_OUTSIDE error will be thrown if a Java application is starting a global transaction after doing a local transaction with a query statement which needs more than one network round trip to return the query data and the DB2 server that it is connected to supports the QueryCloseImplicitCommit feature. (140048) ____________________________________________________________ Type-4 Connectivity: JCC driver has now added two new APIs on com.ibm.db2.jcc.DB2PreparedStatement interface to get estimated rowcount and cost on successful prepare. The two new APIs are int getEstimateRowCount() and int getEstimateCost() to get the estimated rowcount and cost on prepare respectively. (140157) ____________________________________________________________ Type-4 Connectivity: Driver throws an exception with SQLCODE4499 (-4499) with message "A DRDA Conversational Protocol Error was detected. Reason: 0x1245" when calling a stored procedure that returns a scrollable cursor while setting fetchSize to a value greater than 64. This problem has been corrected. (139580) ____________________________________________________________ Type-4 Connectivity: Application hangs in a datasharing environment when some of the members are going down and transactions are getting timeout either from setQueryTimeout() or from Statement.cancel(). This problem has been corrected. (138412) ____________________________________________________________ Type-2 z/OS Connectivity: When invoking SQLJ Stored Procedure with SQLJ Default Context Caching usage, error message with "leftover native statements at disconnect" or other errors may stop the Stored Procedure execution. This problem has been fixed. (139583) ____________________________________________________________ Type-2 z/OS Connectivity: Cancel Thread was not working under 64bit JVM. This has been fixed. (140165) ____________________________________________________________ Type-2 z/OS Connectivity: Due to incomplete driver cleanup between Java stored procedure executions, one or both of the following errors may occur when running SQLJ Java stored procedures: ***** Driver x.xx.xx internal error: xx leftover native statements at disconnect ***** java.lang.Throwable: Leftover Native Statements or java.util.ConcurrentModificationException The problem has been fixed. (138863) __________________________________________________________ Type-2 z/OS Connectivity: Possible SIGSEGV (ABENDS0C4) may occur during JVM shutdown/termination when running JDK 1.5 SR11 (or higher). The problem has been reported in the DB2 Java Stored Procedure environment, and occurs when the Java Stored Procedure WLM environment is quiesced or otherwise ended. Although the problem was reported in the DB2 Java Stored Procedure environment, it is believed that it could also occur in other execution environments. The SIGSEGV occurs when the JVM invokes the sigaction function after the JCC driver's DLL, which has a registered signal handler, has been deleted from storage. Changes have been made in the driver's DLL unload processing to avoid the problem caused by the change in JDK behavior. (139982) ____________________________________________________________ SQLJ All Connectivities: SQLJ Customizer process returned a zero return code when the customization was a success but the SQLJ Bind invoked by it failed. The SQL Binder is invoked automatically by the SQLJ Customizer in a single process. So if the Binder fails, the Customizer should return a non-zero return code. This is now fixed. (141014)
Problem conclusion
The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR.
Temporary fix
Comments
APAR Information
APAR number
PM09693
Reported component name
DB2 ODBC/JDBC/S
Reported component ID
5740XYR02
Reported release
912
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-03-10
Closed date
2010-06-04
Last modified date
2010-12-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK57672 UK57673
Modules/Macros
DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3BA DSNAQ3BB DSNAQ3B1 DSNAQ3B2 DSNAQ3B3 DSNAQ3B4 DSNAQ3B5 DSNAQ3B6 DSNAQ3B7 DSNAQ3B8 DSNAQ3B9 DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ3F1 DSNAQ3F2 DSNAQ3F3 DSNAQ3F4 DSNAQ3L2 DSNAQ3L9 DSNAQ3RM DSNAQ3S1 DSNAQ3S2 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9
Fix information
Fixed component name
DB2 ODBC/JDBC/S
Fixed component ID
5740XYR02
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"912"}]
Document Information
Modified date:
04 March 2021