EM JOBS AND OMS SERVERS HANGED AND GENERATING HUGE TRACING
Last updated on MAY 04, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [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:
kdk key 8102.3:
ncol: 8, len: 48
At database layer you are observing that the process is mostly waiting on "log file sequential read" and is running:
EMD_NOTIFICATION.OMS_FAILOVER (:1, :2);
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms