Clear old alert in Enterprise Manager (EM) manually from database
Posted by Mir Sayeed Hassan on November 26th, 2017
Clear old alert in Enterprise Manager (EM) in Oracle Database
Given alert shows the old alert which is not require to be present in database, Hence need to clear manually as shown below:
Connect with sysman user
[oracle@db-centos ~]$ !sq SQL> select status from v$instance; STATUS ------------ OPEN
SQL> connect sysman/***** Connected
SQL> sho user USER is "SYSMAN"
SQL> SELECT t.target_name, t.target_type, collection_timestamp, MESSAGE, 'exec em_severity.delete_current_severity(''' || t.target_guid || ''',''' || metric_guid || ''',''' || key_value || ''')' em_severity FROM sysman.mgmt_targets t INNER JOIN sysman.mgmt_current_severity s ON t.target_guid = s.target_guid;
TARGET_NAME TARGET_TYPE COLLECTION MESSAGE EM_SEVERITY
—————–
Snapshot Too Old Error detected: SQL ID cg8zk9gazd3wc, Snapshot SCN 0x0000.1e3b2e53, Recent SCN 0x0000.27897582, Undo Tablespace UNDOTBS1, Current Undo Retention 601473.
exec em_severity.delete_current_severity(‘E11F2CE86C335887E1220F25B1059FE2′,’109613CA182F59DA38A43D8C1E79E7AB’,’UNDOTBS1′)
ETICK oracle_database 11-SEP-17
1 job(s) have failed.
exec em_severity.delete_current_severity(‘E11F2CE86C335887E1220F25B1059FE2′,’28C40B1EA7B6590D8A3F50A2BED485AA’,’ ‘)
There are many such unwanted old alert occur in EM ….
To solve this:
SQL> exec em_severity.delete_current_severity('E11F2CE86C335887E1220F25B1059FE2','109613CA182F59DA38A43D8C1E79E7AB','UNDOTBS1') PL/SQL procedure successfully completed.
SQL> commit; Commit complete.
Similarly you can clear entire alerts which is not require in database.
=========Hence tested & verified in our test db==========