EM JOBS AND OMS SERVERS HANG AND GENERATING HUGE TRACING
(Doc ID 1449015.1)
Last updated on DECEMBER 01, 2021
Applies to:Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2]
Information in this document applies to any platform.
You are observing that EM job is stuck and not progressing.
At OS layer EM job process (j00X) is consuming huge amount of CPU and is generating huge trace files with redo dump information; at the beginning of trace file we can see an error ORA-8102 in the following format:
Additionally, Oracle Management Servers (OMS) are waiting for a resource owned by this process.
If the EM job is killed the first OMS servers that runs the same piece of code that EM is running get stuck as EM job was and the others have to wait too.
Problem is reproducible despite database is bounced instance or OMS servers restarted.
Before issue occurred for first time there has been an abrupt termination of a Management servers or Notification jobs.
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