RE: EM12c incidents when restarting OMS

  • From: Brian Pardy <brianpa@xxxxxxxxxx>
  • To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 20 Jun 2014 15:21:49 +0000

Hi Mike,

I used to have a similar issue.  Could you please confirm which version/release 
of EM12c you use?

My fix for this was as follows:

1)      Unsubscribe from the out-of-the-box incident rules in the EM12c.  The 
out-of-the-box rules (at least on EM12c R1, I have not checked recently) 
include notifications for EM12c components (WebLogic domains and servers and so 
on) that I do not wish to receive.

2)      Create custom incident rules for all the targets, target types and 
incident categories for which you DO wish to be notified (eg Database System, 
Listener, MySQL Instance, Agent) and subscribe to these instead.

3)      Configure OOB monitoring for the oracle_emrep OMS and Repository 
target, per MOS note 1472854.1.

I haven't seen an actual crash in my EM12c environment for which I would have 
needed notification since R1+BP1.  Using this setup, and a script that shuts 
down my central agent along with the OMS when I need to bounce EM12c, I do not 
receive any notifications at all from a planned bounce.  I still monitor the 
repository database target just like my other non-OEM databases, but I do not 
monitor any of the internal EM12c components.  This may be more complicated if 
your environment includes other WebLogic targets (mine doesn't, so I ignore 
them all), but you can create target groups to include/exclude specific targets 
from notifications as needed.




Original message:

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Michael Schmitt

Hello,

Does anyone else who uses 12c cloud control have the issue where you get a ton 
of incidents firing off if you shutdown the OMS?

We have incident notifications setup related to the availability of targets, 
and whenever we try to shutdown the OMS we get a ton of pages and emails as a 
result of these.  Was thinking there has to be a way to prevent them from 
kicking off, but haven't found a good answer yet.

Does anyone know a command or workaround for this?

Thanks in advance for the help
Mike

Other related posts: