About Events Based Notification and Automation on Autonomous Database

An event could be a resource lifecycle state change or a system event impacting a resource. For example, an event is emitted on Autonomous Database when a backup or restore operation begins or ends. Using Oracle Cloud Infrastructure Events you can subscribe to events. This allows you to receive notifications or to perform other types of automation for events.

You can subscribe to Autonomous Database events as follows:

See Overview of Events for complete information on Oracle Cloud Infrastructure Events.

See Get Notified of Autonomous Database Events for information on creating event rules.

About Critical Events on Autonomous Database

Critical events on Autonomous Database are issues that cause disruption to the database.

Event Description
AdminPasswordWarning

Provides a message that the Autonomous Database ADMIN password is expiring within 30 days or is expired.

  • If the ADMIN password is within 30 days of being unusable, you receive a warning indicating the date when the ADMIN password can no longer be used.

  • If the ADMIN password expires and is no longer usable, Autonomous Database reports an event that specifies that the ADMIN user password has expired and must be reset.

DatabaseDownBegin

The Autonomous Database instance cannot be opened, or the services such as high, low, medium, tp, or tpurgent are not started or available.

The following conditions do not trigger DatabaseDownBegin:

  • Operations performed during the maintenance window

  • Load balancer, network, or backup related issues

  • A user stopping the instance

This event will not be triggered if you are using Autonomous Data Guard and the standby database is not available due to any of these conditions.

DatabaseDownEnd

The database is recovered from the down state, meaning the Autonomous Database instance is opened with its services, following a DatabaseDownBegin event. DatabaseDownEnd is triggered only if there was a preceding DatabaseDownBegin event.

The following conditions do not trigger DatabaseDownEnd:

  • Operations performed during the maintenance window

  • A user starting the instance

If you are using Autonomous Data Guard and the primary database goes down, this triggers a DatabaseDownBegin event. If the system fails over to the standby database, this triggers a DatabaseDownEnd event.

DatabaseInaccessibleBegin

The Autonomous Database instance is using customer-managed keys and the database becomes inaccessible (state shows Inaccessible).

The following conditions trigger DatabaseInaccessibleBegin:

  • Oracle Cloud Infrastructure Vault master encryption key is deleted.

  • Oracle Cloud Infrastructure Vault master encryption key is disabled.

  • Autonomous Database instance is not able to reach the Oracle Cloud Infrastructure Vault.

DatabaseInaccessibleEnd

If the Autonomous Database instance recovers from the Inaccessible state that generated a DatabaseInaccessibleBegin event, when the database state changes to Available, the database triggers a DatabaseInaccessibleEnd event.

WalletExpirationWarning

This event is generated when Autonomous Database determines that a wallet is due to expire in less than six (6) weeks. This event is reported at most once per week.

This event is triggered when there is a connection that uses the wallet that is due to expire.

Use the event type Autonomous Database - Critical to specify critical events in Event rules.

About Information Events on Autonomous Database

Information events are operations that provide important details about the database lifecycle on Autonomous Database, such as the time when maintenance begins and maintenance ends, or notifications of connections from a new IP address.

The times shown with these events are in UTC.

Event Description

AJDNonJsonStorageExceeded

This event is generated when an Autonomous JSON Database has exceeded the maximum storage limit of 20GB of data stored outside of SODA collections. This limit does not apply to data stored in SODA collections or objects associated with SODA collections, such as indexes or materialized views.

In addition to this event, an email is sent to the account owner. You must either reduce your usage of non-SODA-related data to below the 20GB limit or promote the Autonomous JSON Database to Autonomous Transaction Processing. See Promote to Autonomous Transaction Processing for more information.

APEXUpgradeAvailable

This event is generated when you are using Oracle APEX and a new release becomes available.

APEXUpgradeBegin

This event is generated when you are using Oracle APEX and your Autonomous Database instance begins an upgrade to a new Oracle APEX release.

APEXUpgradeEnd

This event is generated when you are using Oracle APEX and your Autonomous Database instance completes an upgrade to a new Oracle APEX release.

DatabaseConnection

This event is generated if a connection is made to database from a new IP address (the connection has not been made from the specified IP address in the last 30 days).

MaintenanceBegin

This event is triggered when the maintenance starts and provides the start timestamp for the maintenance (this event does not provide the scheduled start time).

MaintenanceEnd

This event is triggered when the maintenance ends and provides the end timestamp for the maintenance (this event does not provide the scheduled end time).

NewMaintenanceSchedule

This event is generated when the maintenance date is updated and the new date is shown on the Oracle Cloud Infrastructure Console.

ScheduledMaintenanceWarning

This event is generated when the instance is 24 hours from a scheduled maintenance and again when the instance is 1 hour (60 minutes) from the scheduled maintenance.

Note:

When Autonomous Data Guard is enabled, any of these events that occur on the standby database do not trigger an Information event.

Use the event type Autonomous Database - Information to specify information events in Event rules.

See View Patch and Maintenance Window Information, Set the Patch Level for information on maintenance windows.