CPU used higher than it should be - problem with EM?

Question

HI Folks,
last week i came into work to find that the EM agent couldn't connect and that the database was down. The database wasn't down as none of my users were complaining and i could do everything apart from look at the home page of EM. It was a problem with the sysman account password, which i changed and updated the emmoms.properties & target.xml file and EM was fine. Since then the CPU usage has been running constantly at 30-40%, whereas before this it ran below 10%. ADDM shows that queries like:
/* OracleOEM */ select metric_name from v$metricname where metric_id = :metrics_id
are consuming CPU time. But ADDM gives no suggestions to tuning these queries.
Oracle 10g R2
Windows Server 2003 ent edition x86 4 cpu's 12GB RAM
Does anyone know of a fix or had a similar issue? Users are not complaining of performance issues so it is not a major issue just now, but it something i would like to get sorted. Any help would be greatly appreciated.

Answer 1

Thanks......
Here is the top5 events from the AWR report:
FINDING 1: 55% impact (232 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 21% benefit (87 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"dj1sv9x4jwtrt".
RELEVANT OBJECT: SQL statement with SQL_ID dj1sv9x4jwtrt and
PLAN_HASH 1975534100
/* OracleOEM */ select metric_name from v$metricname
where metric_id = :metrics_id
RATIONALE: SQL statement with SQL_ID "dj1sv9x4jwtrt" was executed 159034
times and had an average elapsed time of 0.00054 seconds.
RECOMMENDATION 2: SQL Tuning, 18% benefit (74 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"8ac2h3qfqhnxw".
RELEVANT OBJECT: SQL statement with SQL_ID 8ac2h3qfqhnxw and
PLAN_HASH 2703597013
/* OracleOEM */ select metrics_id from v$threshold_types
where alert_reason_id = :reason_id
RATIONALE: SQL statement with SQL_ID "8ac2h3qfqhnxw" was executed 176712
times and had an average elapsed time of 0.00041 seconds.
RECOMMENDATION 3: SQL Tuning, 7.4% benefit (31 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7gskff4xc7qb7".
RELEVANT OBJECT: SQL statement with SQL_ID 7gskff4xc7qb7 and
PLAN_HASH 985549317
/* OracleOEM */ select reason_id, internal_metric_category,
internal_metric_name, scope, type, object_type from
v$alert_types where internal_metric_category = :1
RATIONALE: SQL statement with SQL_ID "7gskff4xc7qb7" was executed 20387
times and had an average elapsed time of 0.0015 seconds.
RECOMMENDATION 4: SQL Tuning, 4.9% benefit (20 seconds)
ACTION: Tune the PL/SQL block with SQL_ID "8uxr3scz9bmxd". Refer to the
"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide
and Reference"
RELEVANT OBJECT: SQL statement with SQL_ID 8uxr3scz9bmxd
/* OracleOEM */ BEGIN :succ_sub := 0;
dbms_aqadm.create_aq_agent(:subscriber); :succ_sub := 1;
EXCEPTION WHEN OTHERS THEN IF SQLCODE =
-24089 THEN NULL; ELSE RAISE; END
IF; END;
RATIONALE: SQL statement with SQL_ID "8uxr3scz9bmxd" was executed 1359
times and had an average elapsed time of 0.015 seconds.
RECOMMENDATION 5: SQL Tuning, 4.7% benefit (20 seconds)
ACTION: Tune the PL/SQL block with SQL_ID "2jhc0tttdtxv6". Refer to the
"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide
and Reference"
RELEVANT OBJECT: SQL statement with SQL_ID 2jhc0tttdtxv6
/* OracleOEM */ BEGIN :succ_sub := 0;
dbms_aqadm.enable_db_access(:subscriber, :username);
:succ_sub := 1; EXCEPTION WHEN OTHERS THEN
IF SQLCODE = -24034 THEN NULL; ELSE RAISE;
END IF; END;
RATIONALE: SQL statement with SQL_ID "2jhc0tttdtxv6" was executed 1359
times and had an average elapsed time of 0.014 seconds.