Event Monitor (EMON) Process Constantly Consuming CPU
(Doc ID 1603844.1)
Last updated on JUNE 11, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Event Monitor (EMON) worker process is consuming CPU.
Multiple stacks from the process obtained via
connect / as sysdba
oradebug setospid 1379
or use the following to find EMON process
In 11g ps -ef | grep EMON
In 12c ps-ef |grep ennn
oradebug SHORT_STACK
have the form
Oracle pid: 43, Unix process pid: 1379, image: oracle@feltux3154 (E000)
_write()+10<-nttwr()+275<-nsntwrn()+111<-nspsend()+935<-nsdo()+4694<-nsfull_sd()+46<-kpcesend()+952<-kponsnd()+392<-kponepms()+1729<-kponprmsg()+405<-kponemn0()+597<-kponemn()+1152<-ksvrdp()+3653<-opirip()+901<-opidrv()+684<-sou2o()+87<-opimai_real()+280<-ssthrdmain()+295<-main()+203<-_start()+108
which indicates it is stuck in a network write.
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 |