Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I setup the OEM with the Idea to receive Critical messages (emails when the DB, listener, agents and host are down/up) but it doesn't seem to be working. If I "shutdown abort" the database I wont received any message until I put it up and running, so I receive all the messages together.

Please see image Bellow, that's how I set the alerts, I tested the Email sending and it's working.

  • Any Idea what it could be?

enter image description here

share|improve this question
just trolling but you aren't rebooting the database where the repository is running on right? because... that would sound logical that way – Munchi Dec 12 '13 at 20:54
@Munchi acctually I have everything installed in a local host making some test to move them to Production, are you saying that this won't work because they need to be separate? – jcho360 Dec 13 '13 at 13:26
@jcho360 "are you saying that this won't work because they need to be separate" -- Well, how do you think it can send alerts if it's down? – Phil Dec 13 '13 at 13:43
@Phil I thought that the Email Manager was separate of the database status, just like MsSQL, thanks for clarify this – jcho360 Dec 13 '13 at 13:53
up vote 0 down vote accepted

And that is why Enterprise Manager Database Control is inappropriate for this kind of monitoring. Enterprise Manager Grid Control/Cloud Control runs on a seperate host, with a seperate repository database, and that is the tool for this job.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.