Oracle Cloud Infrastructure Documentation

Monitor Database Availability

You can monitor the availability status of your Managed Database using various functionalities in Database Management.

  • Go to the Oracle Database fleet summary page, on the left pane select Down in the Lifecycle state filter to view the databases that are down or are being shut down. For information on the Oracle Database fleet summary page, see Monitor the Health of Your Oracle Database Fleet.
  • Go to the Managed database details page, in the Summary section, hover the mouse on the Monitoring status timeline to view the history of the database monitoring status with additional details on the potential root cause and the corresponding ORA error, if any. For information on the Managed database details page, see Monitor and Manage a Specific Managed Database.
  • Go to the Managed database details page, in the Alarm definitions section, create the preconfigured (Oracle-recommended) Monitoring Stopped - Metric collection issue alarm. This alarm is fired when metric collection has failed because the database is down, unreachable, or due to other reasons. For information on Oracle-recommended alarms, see Set Up Alarm Definitions.
    Note

    • The Monitoring Stopped - Metric collection issue alarm in Database Management is not available for Autonomous Databases on Dedicated Exadata Infrastructure.
    • The Monitoring Stopped - Metric collection issue alarm for External Databases and Oracle Cloud Databases is an advanced alarm and its syntax cannot be edited in Database Management. You can edit the Monitoring Stopped - Metric collection issue alarm in the Oracle Cloud Infrastructure Monitoring service, however, it's recommended that you do not edit it.

    Here's more information regarding the metrics used for the Monitoring Stopped - Metric collection issue alarm and the time range within which the alarm is fired.

    Supported Oracle Database Monitoring Stopped.. Alarm Details
    External Databases and Oracle Cloud Databases in ExaDB-C@C The Monitoring Stopped - Metric collection issue alarm is fired when the value of the MonitoringStatus metric in the oracle_oci_database namespace is 0 or if the value is not present. This value denotes that metric collection has failed as the database is down or due to issues related to network, agent, credentials, connection, or missing data.

    Using this Oracle-recommended alarm, you can be notified of the availability status of your database within 5 minutes.

    Note

    To be notified within one minute of an availability issue with an Oracle Cloud Database in ExaDB-C@C, you can use the following Database service events:
    • Database - Critical
    • Database - Information

    For more information on the event types, see:
    Oracle Cloud Databases in the Base Database Service and ExaDB-D The Monitoring Stopped - Metric collection issue alarm is fired when the value of the MonitoringStatus metric in the oracle_oci_database namespace is 0 or if the value is not present. This value denotes that metric collection has failed as the database is down or due to issues related to network, agent, credentials, connection, or missing data.

    Using this Oracle-recommended alarm, you will be notified of the availability status of your database within 5 to 9 minutes.

    Note

    To be notified within one minute of an availability issue with an Oracle Cloud Database in the Base Database Service and ExaDB-D, you can use the following Database service events:
    • Database - Critical
    • Database - Information

    For more information on the event types, see:
    Autonomous Databases Serverless The Monitoring Stopped - Metric collection issue alarm is fired when the value of the DatabaseAvailability metric in the oci_autonomous_database namespace is absent. This value denotes that the database is down, unreachable, or that no data is returned for the metric.

    Using this Oracle-recommended alarm, you will be notified of the availability status of your database within 10 minutes.