Hi
DBA-Mates,
Hope you
all are doing Great. Concurrent Manager is always most important in our Oracle
Apps DBA life like heart of the Apps DBA’s.
Recently we faced the below issue
and found the work-around/solution as shown below.
So we thought,
let us share with you all here... Hope this may useful and helpful either
fresher or experience DBAs.
Concurrent
Manager: Output Post processor Issue
Issue:
Users
reported below error message in Production although OPP was up and actual and
target values were matching. The errors were intermittent in nature.
+-------------
1) PUBLISH -------------+
Unable to
find an Output Post Processor service to post-process request 5874119.
Check that
the Output Post Processor service is running.
+--------------------------------------+
‘Out of
memory’ errors were also reported for Java heap of OPP.
Cause:
Main cause
was that queue table of OPP was corrupted.
Solution:
1. Obviously,
our OPP should be UP and Running status.
And to
check the OPP status, we need to go front-end and check for CM (OPP), the
Actual and Target count should be same or equal.
2. Then we
have to Shutdown all concurrent managers properly.
3. After that
run cmclean.sql
4. Run the
script $FND_TOP/patch/115/sql/afopp002.sql as the APPLSYS user as shown below:
As applmgr:
SQL>
@$FND_TOP/patch/115/sql/afopp002.sql
Enter value
for 1: applsys
Enter value
for 2: *****
5. Start
concurrent managers.
6. Verify
number of rows (number of process for OPP + 2) in
APPLSYS.AQ$_FND_CP_GSM_OPP_AQTBL_S.
Metalink Note Reference: (Doc ID 1399463.1)
Some more useful
links:
Your post is great. I read your blog site fairly often, and you are continuously coming up with some decent staff.
ReplyDeleteI shared this post on my Twitter, and my followers loved it.
Have a great day. Cheers.
Your post is great. I read your website pretty regularly, and you're constantly coming up
ReplyDeletewith some decent staff. I shared this post on my Twitter,
and my followers loved it! Have a nice day. Cheers.
Sweet! Thank you for the review!
ReplyDelete