How to Troubleshoot Notifications That Are Hung / Stuck and Not Being Sent from EM 10g/11g
(Doc ID 285093.1)
Last updated on NOVEMBER 16, 2019
Applies to:Enterprise Manager Base Platform - Version 10.1.0.2 to 18.104.22.168 [Release 10.1 to 11.1]
Information in this document applies to any platform.
This document helps in troubleshooting Enterprise Manager Setup when the Notifications are Hung or are not being sent.
You can follow the steps in this document for these symptoms:
- No Notifications are being sent, when a Metric Alert or Policy Violation is generated against a monitored target, irrespective of the notification method that has been chosen.
However, the Test button for that particular notification method works and test messages are received.
- The 'Notification Delivery Backlog' chart in the Repository is growing linearly.
This chart can be found in 10.1.0.x Grid Console under Management System -> Management Services and Repository
In 10.2 Grid Control and above versions, check under Setup -> Management System and Repository
From the time, the notification was last sent the value grows linearly - but never decreases.
- Errors could exist in the Management System and Repository -> Errors tab
Error Unexpected error during: QUEUE(EMAIL4/<emailaddress>/SYSMAN)
"Unexpected error during queue ORA-25205: the queue SYS.MGMT_NOTIFY_Q does not exist."
- Notifications are being sent but they are delayed - time gap between the actual metric alert and the sent notification is very large.
Note: Sometimes, re-starting the OMS can clear out the problem which is causing the notifications to be stuck. Hence, it is advisable to collect the information listed below, before re-starting the OMS.
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