My Oracle Support Banner

High CPU OEM Metrics On Physical Standby Database (Doc ID 2440665.1)

Last updated on SEPTEMBER 11, 2018

Applies to:

Enterprise Manager for Oracle Database - Version 13.1.1.0.0 and later
Information in this document applies to any platform.

Symptoms

 

following  sql statement in Physical Standby Database take  long time to executing and has a high CPU.

SELECT p.con_id, p.name, TO_CHAR(MAX(CAST(l.execution_end AS TIMESTAMP)), 'DD-MON-YYYY HH24:MI:SSxFF'), TO_CHAR(CAST(sysdate AS TIMESTAMP), 'DD-MON-YYYY HH24:MI:SSxFF') FROM (SELECT con_id, name FROM v$containers where con_id != 2) p LEFT OUTER JOIN cdb_advisor_tasks l ON l.advisor_name = 'Segment Advisor' AND TO_CHAR(CAST(l.execution_end AS TIMESTAMP), 'DD-MON-YYYY HH24:MI:SSxFF') > '01-AUG-2018 05:18:57.000000' AND p.con_id = l.con_id GROUP BY p.con_id, p.name

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.