Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Unable to find an Output Post Processor service to post-process request, FND_CP_GSM_OPP_AQ Queue is Invalidated After Patching
Symptoms:
XML concurrent requests getting failed with the error:
+---------------------------------------------------------------------------+
Executing request completion options...
+------------- 1) PUBLISH -------------+
Unable to find an Output Post Processor service to post-process request 13400761.
Check that the Output Post Processor service is running.
+---------------------------------------------------------------------------+
Executing request completion options...
+------------- 1) PUBLISH -------------+
Unable to find an Output Post Processor service to post-process request 13400761.
Check that the Output Post Processor service is running.
After restarting the completed database and application now OPP log contains below error:
[2/28/10 8:03:54 PM] [UNEXPECTED] [OPPAQMON:97381] Too many SQL errors, shutting down AQ monitor
[2/28/10 8:03:54 PM] [EXCEPTION] [OPPAQMON:97381] java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:1163)
at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:1075)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.unsubscribeFromAQ(OPPAQMonitor.java:574)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:131)
at java.lang.Thread.run(Thread.java:534)
[2/28/10 8:03:54 PM] [UNEXPECTED] [OPPAQMON:97381] Too many SQL errors, shutting down AQ monitor
[2/28/10 8:03:54 PM] [EXCEPTION] [OPPAQMON:97381] java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:1163)
at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:1075)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.unsubscribeFromAQ(OPPAQMonitor.java:574)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:131)
at java.lang.Thread.run(Thread.java:534)
Log files:
Solution:
1. Close concurrent manager and makes sure that there is no FNDLIB processes is running then follow
Note: 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables.
Retest the issue
Note: 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables.
Retest the issue
2. Bug.8337735 (92) XML REPORTS ARE COMPLETED WITH STATUS WANING.:
Reduce the number of OPP processes, ensure that you have only 1 in the OPP processes and change the threads to be 5 instead of 6.
Bounce the CM and retest again.
Reduce the number of OPP processes, ensure that you have only 1 in the OPP processes and change the threads to be 5 instead of 6.
Bounce the CM and retest again.
3. Recreate the queue using $FND_TOP/patch/115/sql/afopp002.sql file as 'APPLSYS' user. On running the script you will be prompted for username and password.
4. Republish those requests to get the real output generated by applying the template.
References:
FND_CP_GSM_OPP_AQ Queue is Invalidated After Patching [ID 311851.1]
No comments:
Post a Comment