ORA-17125: "Improper statement type returned by explicit cache"

Question

I have been using SQLJ to some extent in the current java project but just now I'm getting this error on a particular piece of code which was converted using SQLJ pre-compiler:
// #sql [xtrConnectionContext] { CALL
// XTR_CFNG_DBAPI.pRemoveXTRLotsLogger(:billCycle,
// :billCycleEndDate, :runType) };
     // declare temps
     oracle.jdbc.OraclePreparedStatement __sJT_st = null;
     sqlj.runtime.ref.DefaultContext __sJT_cc = xtrConnectionContext;
     if (__sJT_cc == null)
          sqlj.runtime.error.RuntimeRefErrors.raise_NULL_CONN_CTX();
     sqlj.runtime.ExecutionContext.OracleContext __sJT_ec = ((__sJT_cc
               .getExecutionContext() == null) ? sqlj.runtime.ExecutionContext
               .raiseNullExecCtx()
               : __sJT_cc.getExecutionContext().getOracleContext());
     try {
          __sJT_st = __sJT_ec
                    .prepareOracleStatement(__sJT_cc,
                              "0com.pt.vodafone.xtr_ppb.XTR",
                              "BEGIN XTR_CFNG_DBAPI.pRemoveXTRLotsLogger( :1 , :2 , :3 ) \n; END;");
          // set IN parameters
          __sJT_st.setString(1, billCycle);
          __sJT_st.setString(2, billCycleEndDate);
          __sJT_st.setString(3, runType);
          // execute statement
          __sJT_ec.oracleExecuteUpdate();
     } finally {
          __sJT_ec.oracleClose();
The procedure called has the following declaration:
PROCEDURE pRemoveXTRLotsLogger(pvBillCycle IN VARCHAR2,
pvBillCycleEndDate IN VARCHAR2,
pvExpeditionCode IN VARCHAR2);
The procedure just deletes a few records from a table and works perfectly during testing.
The variables billCycle, billCycleEndDate, runType are all String.
During execution, the ORA-17125 is always returned. It's description is "Improper statement type returned by explicit cache".
One interesting thing was that even replacing the procedure call by the delete itself, the execution also returned the same error.
I'm not using any kind of explicit cache and the connection to the database shouldn't be a problem, because previous statements in the same connection were executed without any problem.
Thanks a for your time.
Best regards,
VP

Answer 1

I solved the problem disabling the statement cache in my connection method:
public DefaultContext connectToDB(String server, String port, String sid, String user, String pass) throws ErrorException {
     DefaultContext connectionContext;
     // DISABLE CONNECTION STATEMENT CACHE!
     DefaultContext.setDefaultStmtCacheSize(0);
     try {
          connectionContext = Oracle.getConnection(oracleJDBCDriver + server
                    + ":" + port + ":" + sid, user, pass, false);
     } catch (SQLException e) {
          throw new ErrorException("Connect to " + sid + " failed.");
     return (connectionContext);
Best regards,
VP