oracle 11g OEM sysman select

High CPU after DB Console start in 11g

SELECT EXECUTION_ID, STATUS, STATUS_DETAIL FROM MGMT_JOB_EXEC_SUMMARY
WHERE JOB_ID = :B3 AND
TARGET_LIST_INDEX = :B2 AND EXPECTED_START_TIME = :B1

[@more@]If you have a problem with Oracle sessions taking a high CPU load in 11g after you start a DB Console check if any of these session is executing following query:

SELECT EXECUTION_ID, STATUS, STATUS_DETAIL FROM MGMT_JOB_EXEC_SUMMARY
WHERE JOB_ID = :B3 AND
TARGET_LIST_INDEX = :B2 AND EXPECTED_START_TIME = :B1

If yes, you can fix it using that steps:

stop DB Console

emctl stop dbconsole
connect as sysman using SQL*Plus execute both procedures

SQL> execute MGMT_PAF_UTL.STOP_DAEMON;
SQL> execute MGMT_PAF_UTL.START_DAEMON;
Start DB Console

emctl start dbconsole

This is reported as bug number 7182962

转载：http://www.ora600.be/node/6561

ITPub博客

oracle 11g 开启 em后，High CPU after DB Console start in 11g

High CPU after DB Console start in 11g

最新文章