EM 12c, EM 13c : How to Disable the Notification Subsystem in the OMS?
(Doc ID 1545952.1)
Last updated on NOVEMBER 27, 2019
Applies to:Enterprise Manager Base Platform - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
This document provides the steps for disabling the Notification subsystem in the OMS. This is useful in certain conditions such as described below:
1. The OMS has been down for sometime due to a maintenance operation but the Agents are running on the monitored machines. When the OMS is brought up, all the Agents will upload their existing severity / alert information causing a flood of events to be raised in the Console. If the incident rules are configured for these events, then many notifications will be sent out for alerts that have occurred in the past (when the OMS was down).
2. The EM Cloud Control Repository has been cloned / copied to a test instance, in order to prepare for upgrades or critical patching or similar scenarios. In this case notification settings, all agent information and the communication keys to communicate with those Agents are stored in the repository. As soon as an OMS is started using this repository, it will start communicating with these live agents.
3. In a multi-OMS setup, there is a requirement to configure only one OMS to send all the notifications and disable the subsystem in the others (possible that the other OMS are behind a firewall and hence cannot communicate with the external entities like the SMTP (mail) server for sending emails).
<Note 2415712.1> : EM 13c: OMS Fails to Start and emctl.msg File Reports Critical error err=3 detected in module Notification Delivery
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