Scribd
Upload
772 views

Event Monitor Slave Process Consuming More Cpu

The EMON slave process in Oracle Enterprise Manager 12c was consuming more CPU usage because it was stuck trying to communicate with an unresponsive client. To resolve this, the process ID of the EMON slave should be killed, the "_client_enable_auto_unregister" value should be changed to TRUE if it is FALSE, and the database should be bounced.

Uploaded by

doyenblog
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
772 views

Event Monitor Slave Process Consuming More Cpu

The EMON slave process in Oracle Enterprise Manager 12c was consuming more CPU usage because it was stuck trying to communicate with an unresponsive client. To resolve this, the process ID of the EMON slave should be killed, the "_client_enable_auto_unregister" value should be changed to TRUE if it is FALSE, and the database should be bounced.

Uploaded by

doyenblog
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Event Monitor slave process consuming more cpu usage

in Oracle Enterprise Manager 12c


Reason:
EMON slave process stuck in a network that tried to communicate with the not
responding client.
Step to do:
1. Kill the process id of the emon slave process.
$ kill -9 ps_id
2. Check the _client_enable_auto_unregister value, if the value is FALSE then change
to TRUE.
$ sqlplus / as sysdba
SQL> alter system set _client_enable_auto_unregister=true
scope=both sid=*;
SQL> Exit;
3. Bounce the database.
$ sqlplus / as sysdba
SQL> Shut immediate
SQL> Startup

You might also like