DB2 - Problem description
Problem IC76342 | Status: Closed |
ARRAYINDEXOUTOFBOUNDSEXCEPTION ON STATEMENT.COMPLETEEXECUTECALL WHEN CALLING PL/SQL STORED PROCEDURE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Users Affected: This problem affects customer using DB2 9.7 in Oracle Compatability Mode, using JDBC to call PL/SQL stored procedures. Error Description: If a PL/SQL stored procedure returns one or more cursors in OUT parameters, and if one or more of these cursors are returned conditionally, the following exception may occur if a cursor is not returned: java.lang.ArrayIndexOutOfBoundsException: <parameter> at com.ibm.db2.jcc.am.km.a(km.java:2123) at com.ibm.db2.jcc.t4.db.l(db.java:607) at com.ibm.db2.jcc.t4.db.k(db.java:333) at com.ibm.db2.jcc.t4.db.e(db.java:96) at com.ibm.db2.jcc.t4.t.e(t.java:81) at com.ibm.db2.jcc.t4.sb.j(sb.java:160) at com.ibm.db2.jcc.am.km.hb(km.java:2113) at com.ibm.db2.jcc.am.lm.b(lm.java:3589) at com.ibm.db2.jcc.am.mm.Yb(mm.java:113) at com.ibm.db2.jcc.am.mm.execute(mm.java:96) ... This exception may occur only if the application is using application-manages prepared statement cache. Conclusion: For a callable Statement, if the procedure name and signature match, the application will get the Callable Statement from the cache. However, the driver was erroneously treating the procedure name, signature and the identifier of the previously-returned result set, as matching. | |
Problem Summary: | |
First fixed in JDBC driver from DB2 9.7 Fix Pack 5 (JCC driver version 3.63.75) | |
Local Fix: | |
Disabling statement cache should circumvent this problem. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to JDBC driver from DB2 9.7 Fix Pack 5 (JCC driver version 3.63.75) | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.05.2011 19.05.2017 19.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |