wood burning stoves 2.0*
The moose likes Oracle/OAS and the fly likes Parameter Type Conflict: sqlType=2003 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Oracle/OAS
Bookmark "Parameter Type Conflict: sqlType=2003" Watch "Parameter Type Conflict: sqlType=2003" New topic

Parameter Type Conflict: sqlType=2003

nandini lagunia
Ranch Hand

Joined: May 05, 2009
Posts: 57
I am using Oracle 9i and jdk 1.4.
I have written a stored procedure that takes Array and returns Array.

For that I've crteated a type like as follows:-
CREATE TYPE workorderArr AS varray(100) OF varchar2(100);

My stored procedure looks like:-

CREATE OR REPLACE PROCEDURE delcust_order_byworkorder_mul (

reqArr IN workorderArr,

responseArr OUT workorderArr



orderstatus INTEGER (2) := 0;

workordernumber VARCHAR (9) :='w';


responseArr := workorderArr('');

FOR i in reqArr.first .. reqArr.last LOOP



Now I am trying to execute this Stored procedure through my java code as follows:-

This program compiles fine but upon running, it gives me following exception:-

java.sql.SQLException: Parameter Type Conflict: sqlType=2003
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.driver.OracleCallableStatement.registerOutParameterBytes(OracleCallableStatement.java:239)
at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java:393)
at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java:462)
at com.ceon.pencor.Test.main(Test.java:45)

I don't have any clue what's wrong with the code.
Any kind of help will be highly appreciated.

Consider Paul's rocket mass heater.
subject: Parameter Type Conflict: sqlType=2003
Similar Threads
invalid name patter error
Passing Array as a parameter to Stored procedures
calling stored function
Size limit on OracleCallableStatement setARRAY ?
Can I call CallableStatement .getObject(int)