• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

Size limit in OracleCallableStatement setARRAY

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sorry for posting this article somewhere else before.

I am trying to pass an array object of type oracle.sql.ARRAY to Oracle stored procedure; most of the times I am successful at that. It was found after a customer reported an error that when the array had certain number of elements in it, the code failed. I didnt find out the exact threshold value at which the code broke. Upto around 1000 elements in the array it worked fine. At 1500 it failed. I am working with WebLogic Server 8.1 SP4, Oracle at client 9.2.0.5 and at server 9.2.0.6. I am using direct JDBC OCI connection and not the Weblogic connection pool. Below is the code which is causing the problem.



Even before the OracleCallableStatement is executed it breaks right at the setARRAY method.

The exception thrown is:
Caused by: java.sql.SQLException: Invalid argument(s) in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.dbaccess.DBItem.setArrayData(DBItem.java:262)
at oracle.jdbc.dbaccess.DBDataSetImpl.setADTBindItem(DBDataSetImpl.java:2738)
at oracle.jdbc.driver.OraclePreparedStatement.setARRAY(OraclePreparedStatement.java:1760)
at com.pearson.report.persistence.StudentMasteryDAO.getStudentMasteryData(StudentMasteryDAO.java:116)
... 8 more

Can someone please help me understand why this exception is thrown? How can I get over this problem?

Thanks,
Vikram Phale.

[ April 10, 2007: Message edited by: Vikram Phale ]
[ April 10, 2007: Message edited by: Vikram Phale ]
 
Vikram Phale
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is a bug introduced in 9.2.0.5.
Bug 4057147 - JDBC OCI returns invalid argument exception when binding over 64kb array.
Using JDBC Thin drive works.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic