Manually Clear Alerts in Oracle Enterprise Manager 11g

In our 11gR2 RAC databse, we got some ORA-00600 errors in the alert log file. These errors have been fixed by applying the oracle patches. But, in the Oracle Enterprise Manager these old alerts are not cleared. To manually clear the alerts, I did the following steps;

1. Go to Enterprise Manager Home Page > select Instance Name > Metrics and policy settings > changed the view to all metrics > Choose the “Generic Internal Error” metric to disable it.

Follow the links below to see the steps;

http://www.oracle-class.com/wp-content/uploads/2011/11/EM1.png

http://www.oracle-class.com/wp-content/uploads/2011/11/EM2.png

http://www.oracle-class.com/wp-content/uploads/2011/11/EM3.png

http://www.oracle-class.com/wp-content/uploads/2011/11/EM4.png

 

2. Go to the Instance from the SSH client > export correct environment for the database instance > as the oracle database software owner issue “emctl clearstate agent” command.

3. Go to console and check the alert is cleared now,

4. To enable the metric now for future alerts; Go to DB Console Home Page > select Instance Name > Metrics and policy settings > changed the view to all metrics > Click on “Generic Internal Error” metric and enable it again by adding the characters “.*” in the critical threshold field and save the changes.

 

You can find the article here: www.oracle-class.com

 

Hope it helps!

Wissem EL KHLIFI

Views: 206

Comment

You need to be a member of Oracle Community to add comments!

Join Oracle Community

Oracle Community On

I'm not a fan of advertising, and so I will not be including any advertisements on OracleCommunity.net. However, managing this community does not come without cost! If you are willing to donate to help pay for the monthly community fees and domain services I accept Bitcoin and PayPal donations.

Donate Bitcoins

Badge

Loading…

Blog Posts

Database hang and Row Cache Lock concurrency troubleshooting

This post will help to analyze Oracle database instance slowdown that can happen due to considerable row cache lock (enqueue) wait events. It’s is based on a real case of a database hang that I worked on recently. I must admit this type of situation does not appear often but it’s very dangerous since it can considerably slow down a database instance or even freeze it for a short period of time. In most cases SQL against ASH view and Systemstate dumps can help to nail down the problem unless…

Continue

Posted by Kirill Loifman on April 15, 2014 at 12:53am

© 2014   Created by Steve Karam.

Badges  |  Report an Issue  |  Terms of Service