My Oracle Support Banner

When Running EM_MONITOR Utility Concurrent Queries are Causing High CPU Spikes (Doc ID 2358602.1)

Last updated on FEBRUARY 07, 2018

Applies to:

Oracle Concurrent Processing - Version 12.2.6 to 12.2.6 [Release 12.2]
Information in this document applies to any platform.

Symptoms

OEM concurrent manager monitoring for EBS is causing high CPU consumption on exadata machine due to hard parsing of queries and not using bind variables.

After running the AWR report, the expensive SQL was identified.
When the FND_CONCURRENT_CRM_REQUESTS and fnd_concurrent_worker_requests views are compiled, it is running a select against the following:

/*+ ORDERED INDEX (r, FND_CONCURRENT_REQUESTS_N7) USE_NL (r p) NO_EXPAND */

This is causing a fixed limit on the number of branches that the _fix_control parameter can expand to.

This parameter is set in the init.ora file.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.