Looks like you are using PL/SQL procedure with Java. Since the error message talks of OVERFLOW, how about changing Types.Integer to some higher datatypes like Types.BIGINT or Types.DOUBLE depending on your need?
please see the comments in the code..
the related log is -
Fri Mar 02 10:38:03 CET 2007,com.abnamro.opp.bm.payment.directdebit.DataAccessClass.java,java.sql.SQLException: Numeric Overflow
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
at oracle.jdbc.driver.NumberCommonAccessor.throwOverflow(NumberCommonAccessor.java(Inlined Compiled Code))
at oracle.jdbc.driver.NumberCommonAccessor.getLong(NumberCommonAccessor.java(Compiled Code))
at oracle.jdbc.driver.OracleCallableStatement.getLong(OracleCallableStatement.java:1155)
at com.ibm.ws.rsadapter.jdbc.WSJdbcCallableStatement.getLong(WSJdbcCallableStatement.java:409)
at com.abnamro.opp.util.jdbc.wrapper.CallableStatementWrapper.getLong(CallableStatementWrapper.java:256 )
at com.abnamro.opp.bm.payment.directdebit.DataAccessClass.methodThatCallsProcedure(DataAccessClass.java .java:838)
at com.abnamro.opp.bm.payment.directdebit.DirectDebitPaymentDataAccess.methodThatCallsProcedure(DataAcc essClass.java465)
at com.abnamro.opp.bm.payment.directdebit.DirectDebitPaymentDataAccess.storeDirectDebitPayment(DataAcce ssClass.java.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
Bookmarks