Today a customer consults with their RAC environment, Emd_maintenance. The Execute_em_dbms_job_procs process starts frequently and consumes a lot of system resources.
This task runs every minute, and it is always in front of the top.
This job is the job that EM uses to maintain management, and the job that causes performance problems is no longer a small number of bugs, such as Bug 7759386.
and customers confirm that they don't use EM at all, the easiest way to solve this problem is to remove the maintenance job.
Use Sysman User Login to execute this sql:
Sql> Conn Sysman
Enter Password:
ERROR:
Ora-28000:the account is locked
Warning:you are no longer connected to ORACLE.
Sql> Conn/as SYSDBA
Connected.
sql> alter user Sysman account unlock;
User altered.
Sql> Conn/as SYSDBA
Connected.
sql> alter user Sysman identified by NewPassword;
User altered.
Sql> Conn Sysman
Enter Password:
Connected.
sql> exec emd_maintenance.remove_em_dbms_jobs;
Pl/sql procedure successfully completed.
Sql> commit;
Commit complete.
In fact, if the user does not intend to use EM, then the establishment of the database without the choice of EM configuration, not only can avoid the impact of EM bugs on the system, but also to avoid EM to the system performance and space losses.