Setting Up Out of Bound (OOB) Notification for 'OMS and Repository' Target in 10g/11g Grid Control (Doc ID 429257.1)

Last updated on JUNE 03, 2014

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.1 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 09.Aug.2013***

Goal

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.

NOTE: As per <BUG 6038172>, when the Grid Control environment is configured with multiple OMS servers, then the Out of Band (OOB) Notification will only generate an email when all OMS servers are 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 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.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms