Output Post Processor (FNDOPP) is not Starting
(Doc ID 837640.1)
Last updated on FEBRUARY 04, 2024
Applies to:
Oracle Application Object Library - Version 11.5.10.2 and laterInformation in this document applies to any platform.
OPP Concurrent Manager
Symptoms
The Output Post Processor (FNDOPP) Manager is not starting, process status is shown as Actual with 0 and the Target is 1
The OPP logfile shows the following exceptions:
[UNEXPECTED] java.sql.SQLException: Closed Connection
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.PhysicalConnection.prepareCall(PhysicalConnection.java:947)
at oracle.jdbc.driver.PhysicalConnection.prepareCall(PhysicalConnection.java:913)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java:419)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:114)
at java.lang.Thread.run(Thread.java:797)
XML Publisher post-processing action complete.
Completed post-processing actions for request 486325.
ORA-01089: immediate shutdown in progress - no operations are permitted
java.sql.SQLException: ORA-01089: immediate shutdown in progress - no operations are permitted
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java:429)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:114)
at java.lang.Thread.run(Thread.java:797)
Changes
Implemented multi node set up.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |