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)

custom managers and processes question

Jan 14, 2016 2:32PM edited Jan 25, 2016 11:34AM in Core Concurrent Processing - EBS (MOSC) 13 commentsAnswered ✓

EBS R12.1.3 running on a two tier Red Hat 5.10 setup.

I was asked to look into creating a Custom Manager based on some assumptions that jobs are getting queued up behind longer running jobs.

Now I think there are ways to look into this via the application or by using the afcm*.sql scripts in $FND_TOP/sql but I am mostly wondering about

some of the settings you use when it comes to creating a Custom Manager.

For example my app server has 8 cores and Standard Manager is defined with 16 processes and a cache size = 32.

Is the 16 processes configured as a reflection of the number of cores my server has or just a reflection of workload or both?

0

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