Troubleshooting
Problem
Contains list of shipped APARs for the IBM® Data Server Driver for JDBC and SQLJ Version 9.5. APARs sorted by fix pack.
Resolving The Problem
Tab navigation
- V10.5 JDBC
- V10.1 JDBC
- V9.7 JDBC
- V9.5 JDBC - selected tab,
- V9.1 JDBC
************************************************************
Product Name : IBM® Data Server Driver for JDBC and SQLJ Version 9.5
Updated : January 20, 2014
************************************************************
Select a Fix Pack: 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1
| DB2 JDBC Version 9.5 Fix Pack 10 |
| APAR No. | Abstract |
| IC77102 | NULLPOINTEREXCEPTION IS THROWN BY JCC WHEN AN APPLICATION TRIES TO USE LOBS ON A TYPE 2 LUW XA CONNECTION. |
| IC79655 | QUERY GENERATOR IS NOT CHECKING IF COLUMN NAME IS CASE SENSITIVE AND USING COLUMN NAME WITHOUT QUOTES RESULTING IN EXCEPTION |
| IC78921 | SQL0751N WHEN A JCC APPLICATION CALLS A STORED PROCEDURE WITHIN AN XA TRANSACTION, 1- PHASE COMMIT USING TYPE 4 JCC DRIVER |
| LI76407 | JDBC DRIVER GETS ARRAYINDEXOUTOFBOUNDSEXCEPTION FROM BASECALENDAR.GETCALENDARDATEFROMFIXEDDATE |
| IV08650 | SQLJ FINALIZER EARLY CLOSES CAUSE 'OBJECT CLOSED' ON RESULTSETS/STATEMENTS, HUNG DB2 ROUTINES, WAS INDEXOUTOFBOUNDS |
| IC80807 | DISCONNECTRECOVERABLEEXCEPTION WHEN 9.5FP8 CLIENT ACCESS TO 9.7FP4 OR HIGHER SERVER WITH JCC DRIVER |
| IC80319 | JCC DRIVER MAY UN-INTENTIONALLY ALLOCATE MORE CONNECTIONS |
| IC81352 | CALLABLESTATEMENT GETOBJECT () CALL DOES NOT RETURN DATA TYPE BASED ON THE REGISTEROUTPARAMETER TYPE |
| IC81588 | DATABASEMETADATA CALLS TO DB2 FOR Z/OS |
| IC81984 | IF THE SERVER IS LUW(PURESCALE) ,THE JCC WILL TRY TO TRY TO FIND THE BEST MEMBER BY MAKING SOCKET EVEN THOUGH IT MIGHT STILL LIS |
| IC82557 | JCC MIGHT THROW -4471 WHEN CLOSING XA CONNECTION DUE TO INACCURATE STATE MAINTENANCE OF XA TRANSACTION. |
| IC84378 | JCC T4 INCORRECTLY RETRIEVES SOME JAPANESE MULTI-BYTE KANJI CHARACTORS FROM IBM-932 DATABASE. |
| DB2 JDBC Version 9.5 Fix Pack 9 |
| No new APAR's were released for this fix pack. |
| DB2 JDBC Version 9.5 Fix Pack 8 |
| APAR No. | Abstract |
| IC72950 | JCC DRIVER MIGHT MAKE TWICE AS MANY CLIENT REROUTE CONNECTION ATTEMPTS AS ARE CONFIGURED BY MAXRETRIESFORCLIENTREROUTE |
| IC72971 | AFTER TAKEOVER HADR, JAVA APPLICATION REPEATEDLY TRIES TO DO AUTOMATIC CLIENT REROUTE TO THE NEW HADR STANDBY SERVER. |
| IC74050 | JCC DRIVER MEMORY LEAK ON GETNULLCONNECTION FUNCTION. |
| IC74896 | DB2 JCC DRIVER MIGHT THROW EXCEPTION "JAVA.IO.CHARCONVERSIONEXCEPTION". |
| IC75019 | -4470 WHEN ENABLECONNECTIONCONCENTRATOR IS SET TO TRUE AND A HELD CURSOR USED. |
| IC75550 | JDBC DRIVER STUCK IN CLIENT REROUTE |
| IC73312 | XARESOURCE.START FAILS WITH XAER_INVAL, ERRORCODE=-4228 IF SUPPORT FOR LOOSELY-ENABLED TRANSACTIONS ENABLED |
| DB2 JDBC Version 9.5 Fix Pack 7 |
| APAR No. | Abstract |
| IC69089 | JDBC/JCC DRIVER ACCEPTS JDBC:DEFAULT:CONNECTION WHEN RUNNING ON CLIENT SIDE. |
| LI75508 | TYPE 4 JDBC APPLICATIONS CONNECTING TO A DB2 ON Z/OS SYSPLEX OR DB2 PURESCALE SERVER MIGHT HANG AFTER A NOROUTETOHOSTEXCEPTION |
| IC70072 | CONNECTING TO A DATABASE BEING DONE CONCURRENTLY FROM SEVERAL THREADS MAY FAIL WITH JAVA.UTIL.CONCURRENTMODIFICATIONEXCEPTION |
| IC69477 | UNIVERSAL JDBC TYPE 4 APPLICATION RECEIVES ERROR. A DRDA DATA STREAM SYNTAX ERROR WAS DETECTED. REASON: 0X2. ERRORCODE=-4499 |
| IC69458 | JCC DRIVER HANGS IN INFINITE LOOP |
| DB2 JDBC Version 9.5 Fix Pack 6 |
| APAR No. | Abstract |
| IC64787 | IBM DATA SERVER DRIVER FOR JDBC 3 MAY NOT LOAD IN JRE 5.0+ WHEN USING SECURITY MANAGER. |
| IZ64440 | SQLCODE -805 OCCURS ON THE NEXT SQL FOLLOWING A RESET OF JDBC CONNECTION FOR AN APPLICATION RUNNING UNDER WAS |
| IZ64929 | JCC DISCONNECTEXCEPTION ACTUAL CODE POINT, 47 DOES NOT MATCH EXPECTED CODE POINT, 9224 ON CALL TO DB2/Z STORED PROCEDURE |
| LI74666 | WITH DATA SHARING GROUP MEMBERS ON DIFFERENT ZOS LPARS, THE JCC PROPERTY CURRENTSCHEMA MIGHT NOT WORK, SO YOU GET ERROR SQL0204 |
| IC64161 | GETGENERATEDKEYS RETURNS A NULL RESULTSET INSTEAD OF THE ACTUAL GENERATED IDENTITY VALUES |
| LI74750 | NULLPOINTEREXCEPTION FROM JAVA.UTIL.LINKEDLIST$LISTITR.REMOVE |
| IC67562 | SQL0906N ERROR AFTER REBOUND WITH REOPT OPTION |
| IZ55547 | Websphere App Server datasource connects first to DB2 LUW then DB2 on zSeries, zSeries connection will return -104 (SQL0104N) |
| IZ60647 | GETJCCSPECIALREGISTERPROPERTIES() THROWS -4700 ERROR AGAINST DB2Z/OS DATABASES RUNNING IN COMPATIBILITY MODE |
| IC66104 | COMMUNICATIONS ERROR MESSAGE '{1} IS NULL' FROM IBM DATA SERVER DRIVER FOR JDBC AND SQLJ, ON T4AGENT.SENDREQUEST() |
| IC66916 | JCC APPLICATION RETURN -4499 "UNSUPPORTED DDM OBJECT CODE POINT:0X220A" WHILE PROPERTY DEFERPREPARES = TRUE |
| IZ72547 | DB2 JCC TYPE4 DRIVER FORGETS THE CURRENTSCHEMA VALUE IF ROLLBACKIMMEDIATELY AFTER A NEW CONNECTION AND ENABLESYSPLEXWLB=TRUE |
| IC67628 | JCC SQLJ BATCH INSERTS RETURNS ARRAYINDEXOUTOFBOUNDSEXCEPTION |
| IC67695 | XAER_OUTSIDE, hang or connection leak in JDBC/JCC driver |
| IC62516 | IMPLEMENT NEW FLOATINGPOINTSTRINGFORMAT PROPERTY |
| IC64969 | JCC THROWS SQLEXCEPTION WITH ERROR CODE -4476 WHEN PREPAREDSTATEMENT.EXECUTEQUERY() DOESN'T RETURN A RESULTSET. |
| LI74394 | THE UNIVERSAL JDBC DRIVER (JCC) DOES NOT RETURN METADATA WHEN RUNNING A JAVA ROUTINE WHICH RETURNS EMPTY RESULTSET |
| JR32368 | SQLEXCEPTION WITH ERROR CODE -4499 USING THE JCC DRIVER WHEN CONNECTED TO A DATABASE WITH CCSID 1153 |
| IZ40382 | UNIVERSAL JDBC DRIVER FAILS TO RESOLVE INDOUBT TRANSACTIONS WHEN MORE THAN ONE MEMBER OF A DB2/Z DATASHARING GROUP IS AVAILABLE |
| IZ50347 | CONNECTION REQUEST MAY HANG IF AN APP SIMULTANEOUSLY OPENS CONNECTIONS USING DRIVERMANAGER AND DATASOURCE USING JCC DRIVER |
| IC65277 | USING THE JCC DRIVER, GETTIMESTAMP METHODS OF RESULTSET RETURN A SUBCLASS OF JAVA.SQL.TIMESTAMP |
| IZ73137 | METHOD GETUPDATECOUNT RETURNS -1 FOR BATCH UPDATES USING JCC |
| IC65641 | AMBIGUOUS CURSOR IS DELETABLE BUT NOT UPDATABLE |
| IZ69168 | CLASS.GETCLASSLOADER() MAY RETURN NULL IN SOME SITUATIONS |
| LI74705 | SQLCODE -805 RETURNED BY IBM DB2 DRIVER FOR JDBC AND SQLJ BOTH CURRENTPACKAGEPATH AND CURRENTFUNCTIONPATH SET |
| DB2 JDBC Version 9.5 Fix Pack 5 |
| APAR No. | Abstract |
| IZ18902 | INDOUBT TRANSACTIONS APPEAR WHEN DIFFERENT XA RESOURCE IS USED. |
| JR30238 | New property decimalSeparator for the JCC driver to specify the decimal separator. |
| LI73812 | JDBC DRIVER DOESNT CAPTURE THE SQLWARNING AT PREPARE STAGE, PROPERLY |
| LI73560 | JAVA EXCEPTION - ILLEGALSTATEEXCEPTION: TIMER ALREADY CANCELLED |
| JR31251 | IBM DB2 DRIVER FOR JDBC AND SQLJ (JCC) IS NOT ABLE TO SPECIFY ALTERNATE UNICODE CODEPAGE CONVERTER. |
| LI74750 | NULLPOINTEREXCEPTION FROM JAVA.UTIL.LINKEDLIST$LISTITR.REMOVE |
| IZ58007 | JCC DOES NOT SEND A COMMIT WHEN A Z/OS STORED PROCEDURE OR BATCHED QUERY RESULTSET EARLY CLOSES AND AUTOCOMMIT IS TRUE. |
| JR32081 | JCC DRIVER NOT WORKING CORRECTLY WITH PREDICTIVE GOVERNOR IN DB2V8, THUS CAUSING APPLICATION TO FAIL WITH A -30002 ERROR CODE |
| IZ50347 | CONNECTION REQUEST MAY HANG IF AN APP SIMULTANEOUSLY OPENS CONNECTIONS USING DRIVERMANAGER AND DATASOURCE USING JCC DRIVER |
| IZ55547 | Websphere App Server datasource connects first to DB2 LUW then DB2 on zSeries, zSeries connection will return -104 (SQL0104N) |
| IZ40382 | UNIVERSAL JDBC DRIVER FAILS TO RESOLVE INDOUBT TRANSACTIONS WHENMORE THAN ONE MEMBER OF A DB2/Z DATASHARING GROUP IS AVAILABLE |
| LI74394 | THE UNIVERSAL JDBC DRIVER (JCC) DOES NOT RETURN METADATA WHEN RUNNING A JAVA ROUTINE WHICH RETURNS EMPTY RESULTSET |
| DB2 JDBC Version 9.5 Fix Pack 4 |
| APAR No. | Abstract |
| IZ38292 | S04E RC00E70005 DSNXGRDS. DSNXEPAR :M120 ON ZOS WHEN CURRENTFUNCTIONPATH SET TO VALUE CONTAINING ", CURRENT PATH" |
| IZ39352 | JCC DRIVER NOT CHAINING COMMIT ON CURSOR CLOSE |
| JR31711 | THE V9 JCC DRIVER FAILOVER FUNCTIONALITY IS NOT BACKWARDS COMPATIBLE WITH THE V8 JCC FUNCTIONALITY |
| IZ39737 | INSERT OF VARGRAPHIC VALUES WITH TRAILING SPACES FAIL WHEN USINGV9 JCC T4 DRIVER |
| IZ40382 | UNIVERSAL JDBC DRIVER FAILS TO RESOLVE INDOUBT TRANSACTIONS WHENMORE THAN ONE MEMBER OF A DB2/Z DATASHARING GROUP IS AVAILABLE |
| IZ43314 | NULLPOINTEREXCEPTION MAY OCCUR USING BLOB,CLOB,DBCLOB,OR XML OUTPARAMTERS ON CALLABLESTATEMENT IF PROGRESSIVE STREAMING ENABLED. |
| JR31309 | CLIENT REROUTE WITH THE JCC DRIVER SHOULD BE SUPPORTED/ENABLED VIA SYSPLEX WORKLOAD BALANCING AGAINST DB2 FOR Z/OS. |
| LI73765 | N THE THREAD DUMP, IT APPEARS LOT OF THREADS IS WAITING FOR A JAVA.UTIL.VECTOR, HOWEVER, IT DOES NOT SHOW IN THE DUMP |
| IC58566 | BATCHED STATIC SQL PACKAGES FAILING WITH -312 |
| IZ36247 | JCC NOT CLEANING LOGWRITERS IN CASE OF CONNECTION FAILURE |
| LI73949 | JDBC API RESULTSET.GETSTRING() RETURNS DIFFERENT FORMATS FOR BIGDECIMAL NUMERIC VALUE BETWEEN JDK 1.4 AND JDK 1.5. |
| IZ43769 | JCC DRIVER PERFORMING SLOWLY WHEN FETCHING DECFLOAT DATATYPES. |
| DB2 JDBC Version 9.5 Fix Pack 3 |
| APAR No. | Abstract |
| JR3036 | JCC TYPE 4 CONNECTION HANGS WHEN GOING TO A DB2 CONNECT TO A ISERIES (V6R1) |
| JR30534 | MEMORY LEAK IN VECTOR FIELD OF COM.IBM.DB2.JCC.AM.CONFIGURATION,SUBCLASS OF COM.IBM.JCC.DB2BASEDATASOURCE |
| IZ28794 | IBM DB2 DRIVER FOR JDBC AND SQLJ TRUNCATES TRAILING ZEROS WHEN RETRIEVING STRING VALUE FOR TIMESTAMP BY RESULTSET.GETSTRING(). |
| JR30620 | CSTMT.SETOBJECT(INT, CHARDATA) AND CSTMT.SETSTRING(CHARDATA) FAILED IF CHARDATA IS GREATER THAN 32KB |
| IZ22295 | AFTER DB2 SERVER RETURNS ABNUOWRM MESSAGE FOR SQL0911 ERROR, JCCDRIVER BLOCKS ALL LOCAL TRANSCATIONS WITH ERRORCODE=-4497. |
| IZ32618 | DEADLOCK SITUATION OBSERVED WHEN TWO OR MORE BATCH PROGRAMS RUN CONCURRENTLY ON SERVER WAS XA EDITION. |
| JR29617 | JCC DRIVER PROPERTY DOWNGRADEHOLDCURSORSUNDERXA=TRUE CLOSING CURSOR FOR XA LOCAL TRANSACTIONS RESULTING IN -4470 |
| DB2 JDBC Version 9.5 Fix Pack 2 |
| APAR No. | Abstract |
| IZ21339 | JCC DRIVER RETURNS XAER_PROTO |
| IC57215 | INVOKING A Z/OS SP VIA DATASTUDIO 1.1.1 MAY RESULT WITH -4499 |
| IZ10808 | ADD SUPPORT FOR JAVA 1.5 CHANGES TO BIGDECIMAL IN THE UNIVERSAL JDBC DRIVER |
| IZ15539 | THE NUMBER OF RETRIES FOR CLIENT REROUTE IS DOUBLED THAN THE MAXRETRIESFORCLIENTREROUTE SET. |
| IZ19157 | DB2 MAY HIT SIGSEV PROBLEM IF ERROR IS ENCOUNTERED DURING INSERT/DELETE/UPDATE/SELECT THROUGH INDEX |
| LI73362 | SETTING NON-ZERO QUERYTIMEOUT IN THE UNIVERSAL JDBC DRIVER MAY RESULT IN HIGH MEMORY USAGE IN HIGH THROUGHPUT ENVIRONMENTS |
| JR29176 | SQL ERROR -4700 WHEN USING JCC DRIVER 3.X TO CONNECT TO DB2 Z/OS V8 IN COMPATIBILITY MODE |
| DB2 JDBC Version 9.5 Fix Pack 1 |
| APAR No. | Abstract |
| IY98375 | T4 XA TEST HANGS USING GATEWAY |
| IZ01099 | TO ENABLE RESETDB2CONNECTION() AGAINST DB2 UDB V9 |
| IZ04224 | THE JAVA APPLICATIONS ARE HUNG OR UNABLE TO CONNECT WHEN A SYSPLEX MEMBER IS RESTARTED AFTER ALL THE MEMBERS WERE DOWN |
| IZ04652 | GETS -805 ERROR WHEN SYSPLEXWLB IS ENABLE & CURRENTFUNCTIONPATH,CURRENTPACKAGESET PROPERTY ARE SPECIFIED IN THE DATASOURCE |
| IZ07301 | XAER_NOTA ON XA END, IF CALLING ROUTINE WHICH PERFORMS COMMIT ONRETURN |
| JR27848 | JCC: DATABASEMETADATA GETUSERNAME() NOT RETURNING CORRECT RESULT |
| LI72608 | JCC DRIVER NOT CHAINING DRDA BUFFERS CORRECTLY WHEN IN AUTOCOMMIT MODE WITH AUTO GENERATED KEYS & LOB COLUMNS |
| LI72814 | SOME CLASS FILES IN DB2JCC.JAR (JCC DRIVER) ARE CORRUPT. |
| IZ03496 | -4212: NO MEMBER OF SYSPLEX AVAILABLE FROM JCC DRIVER. |
| IZ07562 | BLOB.GETBYTES(1,0) THROWS SQLEXCEPTION |
| JR27842 | TYPE 4 UNIVERSAL JCC DRIVER RETURNS WRONG VALUE FOR DATABASE METADATA FUNCTIONS AGAINST ISERIES. |
Related Information
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Programming Interface - JDBC","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.5","Edition":"Enterprise Server;Express;Personal;Personal Developer's;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Product Synonym
DB2 JDBC Driver
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21414955