- OracleApps Epicenter - http://www.oracleappshub.com -
Output Post Processor – OPP – Troubleshooting 2 common issue
Posted By Sanjit Anand On November 28, 2010 @ 12:25 pm In AOL | No Comments
Before getting insight on two common issue , read this post on "Output Post Processor – OPP "
I S S U E # 1: This error often you get.
The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.
- You need to set the Profile Option "Concurrent: OPP Response Timeout" to a higher value may be necessary.
- If the value of the Profile Option „Concurrent:OPP Response Timeout. is 120 then increase it to 240. (Value * 2).
- Increase the number of processes or threads (or both) .
I S S U E # 2 :Program end-up with this error.
The Concurrent Manager has timed out waiting for the Output Post Processor to finish this Request.
Check that there are enough Output Post Processor Service Processes running. More information may be found in the Service Process logfile.
For example: Set the value to 10800 sec (3 hours). After this change, the Concurrent Request will wait maximum 3 hours, for the Output Post Processor to finish the Request.
hope this helps.
Article printed from OracleApps Epicenter: http://www.oracleappshub.com
URL to article: http://www.oracleappshub.com/aol/output-post-processor-opp-troubleshooting-2-common-issue/
URLs in this post:
 Output Post Processor – OPP: http://www.oracleappshub.com/aol/output-post-processor-opp/
Disclaimer The opinions expressed here represent solely my own represent personal conjecture based upon experience, practice and observation and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients. Copyright © 2007-2010 OracleApps Epicenter. All rights reserved.