Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Core Concurrent Processing - EBS (MOSC)

R12.2.4 OPP process request log

Apr 6, 2017 11:47AM edited Apr 18, 2017 5:01AM in Core Concurrent Processing - EBS (MOSC) 2 commentsAnswered

Currently in our env we have 2 processors running for OPP. For High volume reports we are seeing the reports are failing due to OutOfMemory error.

and at times this clogs the processor and brings the OPP down - users can't run any more XML reports.

The only solution is to bounce the Concurrent Manager.

We are thinking of writing a script to monitor the OPP log and proactively work on the issue if we run into OutofMemory issue.

Do we have any solution for High volume reports to not run into Out Of Memory error ?

Also how do I get the OPP log file names that are associated to Active OPP ?

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month