Troubleshooting
Problem
The workflow calls a stored procedure and since the upgrade of Oracle JDBC Driver from 11g to 12c the stored procedure call has been failing. Process Engine fails at DbExecute step with error FNRPE1210001000E Database error. Cannot bind input to database statement. Other stored procedures are executing without any problems.
Symptom
pesvr trace log captures below error(s):
2016/07/15 20:22:48.953+0200 CMDp.OSD79DA PEPrimary3 DB=FNSSADS
Reg#1 [Error] FNRPE2131090227E ISI Exception (Wob
854A356618B40C408FCF4EE83AF77B85); Exception: Stored Procedure Call
exception "SSA.FJA$SSA.P_SET_BVL"
at filenet.jpe.definitions.DbSPExecute.evalStoredProcedure
(DbSPExecute.java:159)
at filenet.jpe.definitions.DbExecuteWorkOrder.
evalStoredProcedure(DbExecuteWorkOrder.java:266)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
executeOpDbExecute(InstructionSheetInterpreterClass.java:4784)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
doAdvance(InstructionSheetInterpreterClass.java:2923)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
executeOpCreate(InstructionSheetInterpreterClass.java:4763)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
doAdvance(InstructionSheetInterpreterClass.java:2739)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
doExecute(InstructionSheetInterpreterClass.java:2009)
at filenet.jpe.server.isi.InstructionSheetInterpreterClass.
advance(InstructionSheetInterpreterClass.java:997)
at filenet.jpe.cm.CMExecuteAStepTask._saveStep
(CMExecuteAStepTask.java:556)
at filenet.jpe.cm.CMExecuteAStepTask.dispatchStep
(CMExecuteAStepTask.java:392)
at filenet.jpe.cm.CMExecuteAStepTask.doMyJob(CMExecuteAStepTask.
java:334)
at filenet.jpe.cm.CMDispatcherTask.process(CMDispatcherTask.
java:408)
at filenet.jpe.cm.CMDispatcherTask.doMyJob(CMDispatcherTask.
java:170)
at filenet.jpe.cm.CMBaseTask.doJob(CMBaseTask.java:103)
at filenet.jpe.server.common.DelayBackgroundTask.run
(DelayBackgroundTask.java:232)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: [FNRPE1210001000E]Database error. See chained exception
; Cannot bind input to database statement, SQL: "{call SSA.
FJA$SSA.P_SET_BVL
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?
)}"
at filenet.jpe.database.DbDesc.MapOracleError(DbDesc.java:1226)
at filenet.jpe.database.DbDesc.ConvertError(DbDesc.java:1131)
at filenet.jpe.database.DbCallableStatement.convertError
(DbCallableStatement.java:90)
at filenet.jpe.database.DbCallableStatement.getObject
(DbCallableStatement.java:176)
at filenet.jpe.definitions.DbSPExecute.evalStoredProcedure
(DbSPExecute.java:148)
... 17 more
Caused by: java.sql.SQLException: Numeric Overflow
at oracle.jdbc.driver.NumberCommonAccessor.throwOverflow
(NumberCommonAccessor.java:4170)
at oracle.jdbc.driver.NumberCommonAccessor.getInt
(NumberCommonAccessor.java:179)
at oracle.jdbc.driver.OracleCallableStatement.getInt
(OracleCallableStatement.java:1815)
at oracle.jdbc.driver.OracleCallableStatementWrapper.getInt
(OracleCallableStatementWrapper.java:780)
at filenet.jpe.database.DbCallableStatement.getObject
(DbCallableStatement.java:133)
... 18 more
Cause
The stored procedure uses IN direction for the parameters, but our documentation requires IN OUT for Oracle.
Environment
P8 5.2.1 Oracle 11g upgrade to 12c
Diagnosing The Problem
Review the stored procedure definition.
Resolving The Problem
All parameters of the stored procedure should be declared as IN OUT parameters, even when it is not the case.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21990428