Setting Up Out of Bound (OOB) Notification for 'OMS and Repository' Target in 10g/11g Grid Control
(Doc ID 429257.1)
Last updated on AUGUST 18, 2021
Applies to:Enterprise Manager Base Platform - Version 10.2.0.1 to 126.96.36.199 [Release 10.2 to 11.1]
Information in this document applies to any platform.
The following will describe how to setup Out-of-Bound EMail notification to detect when the Oracle Management Service (OMS)/Oracle Management Repository (OMR) goes down.
The agent on the OMS host will check the OMS/OMR status by running the perl script <AGENT_HOME>/sysman/admin/scripts/emrepresp.pl. This calls the <AGENT_HOME>/bin/emrepdown.pl to verify if the OMS/Repository is down.
Requirements to have out-of-bound notification working:
- The sendmail service for OS platform is configured correctly.
- The <AGENT_HOME>/sysman/config/emd.properties is configured with the appropriate *_email_* parameters.
- The oracle_emrep target needs to exist in the <AGENT_HOME>/sysman/emd/targets.xml file. To identify this Agent, use the steps in <Note 604311.1>: How To Find which Grid Control agent is monitoring the target "OMS and Repository" in case of multiple OMS.
The Out-of-bound Notifications are responsible for notifying the user about the following:
a) Repository Database goes down.
b) All OMS go down.
c) Repository side collection job is broken Or it has invalid schedule.
d) The notification job is broken Or it has invalid schedule.
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
|A. Configure OS sendmail Service|
|B. Configure Email Settings in Agent's emd.properties|
|C. Perform a Test Notification|