Concurrent Managers are consuming high CPU and memory
(Doc ID 1075684.1)
Last updated on JULY 18, 2022
Applies to:Oracle E-Business Suite Performance - Version 22.214.171.124 to 12.1.3 [Release 11.5.10 to 12.1]
Oracle Concurrent Processing - Version 126.96.36.199 to 12.1.3 [Release 11.5 to 12.1]
Oracle Application Object Library - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Overall database performance degrades and FNDLIBR processes consumes high CPU and memory on the server.
AWR reports point to following SQLs with very high execution counts :
Manager log files are also flooded with the following messages:
Cause: UPDATE_STATUS failed due to ORA-01002: fetch out of sequence.
The SQL statement being executed at the time of the error was: update
fnd_concurrent_requests set phase_code = :phase ,status_code = :status,
completion_text = :text where request_id = :reqid and was executed from the
file &ERRFILE. User XXX or Responsibility YYYY has expired. Cannot
process request XXXX. APP-FND-01564: ORACLE error 1002 in UPDATE_STATUS
This problem usually affects 11G database users. But problem is also reported against 9i and 10G databases.
Upgraded database to 11G .
End dated a user or a responsibility of a user, but there is a scheduled request.
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