-
Titre
Oracle Availability rules don't fire when a database goes down or is unavailable -
Description
The DBO - Usability rules do not fire, and/or create an alarm, and/or send an email notification when a monitored database instance is down or stopped.
-
Cause
- The rule, alarm or email notification is in a disabled state.
- There is no email address configured to send the notification to.
- The email address to send notifications is incorrect.
- The Rule, Alarm or Email notification is disabled by default in an out of the box configuration.
- Check the FGLAM support bundle during the time of the instance outage to see if the FGLAM agent had a problem communicating to the FMS (Foglight Console)
-
Résolution
Resolution 1:
Enable the Rule under: Administration|Rules & Notifications|Rule Management, or under Agent Global Administrion|Alarms
Verify the Alarm is enabled, and if required the Alarm Email Notification setting is also enabled and a valid email address is configured.
Resolution 2:If the FGLAM agent log states "Error transmitting message to upstream server" with correlation to the time of the instance outage. This illustrates a communication or network problem between the FGLAM to the FMS.
Then, search for "com.quest.glue.core.comms.transport.http.Client - Flushing all pending messages the upstream server." message and this will prove at what time the FGLAM agent got reconnected to the FMS.
This will show if the FGLAM agent was unable to send an alarm based on the Usability alarm during the instance outage.Also, check if the Usability data appears under Configuration | Data | Management Server | expand All Agents | expand instance with the concern | scroll to the bottom and expand Usability