Use Autonomous Database Events

Oracle Cloud Infrastructure Events enable you to create automation based on state changes for your Autonomous Database.

You can use Oracle Cloud Infrastructure Events to subscribe to and be notified of Autonomous Database events. The Oracle Cloud Infrastructure Events allow you to create automation and to receive notifications based on state changes for resources.

• About Events Based Notification and Automation on Autonomous Database
  You can subscribe to Oracle Cloud Infrastructure Events.
• Critical Events on Autonomous Database
  Critical events on Autonomous Database are issues that cause disruption to the database.
• Information Events on Autonomous Database
  Information events 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. Information events are also available to provide details for some operations on Autonomous Database, such as when a workload capture or operator access is initiated.
• Get Notified of Autonomous Database Events
  Using Oracle Cloud Infrastructure Events you can subscribe to Autonomous Database events individually or in two categories, Critical and Information events.

About Events Based Notification and Automation on Autonomous Database

You can subscribe to Oracle Cloud Infrastructure Events.

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. Subscribing to events allows you to receive notifications or to perform other types of automation for events.

You can subscribe to Autonomous Database events as follows:

• Critical Events: See Critical Events on Autonomous Database for details on the events in the Critical event category.
• Information Events: See Information Events on Autonomous Database for details on the events in the Information event category.

• Individual Events. See Database Service: Autonomous Database Event Types for the list of Autonomous Database events.

• Autonomous Data Guard Events. See Events and Notifications for a Standby Database for the list of Autonomous Data Guard events.

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.

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.
AutomaticFailoverBegin	When an automatic failover begins for the Autonomous Database and the database is unavailable an AutonomousDatabase-AutomaticFailoverBegin event is generated. The event will only be triggered if you are using Autonomous Data Guard.
AutomaticFailoverEnd	When an automatic failover that was triggered is complete and the database is now available an AutonomousDatabase-AutomaticFailoverEnd event is generated. The event will only be triggered if you are using Autonomous Data Guard.
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.
FailedLoginWarning	If the number of failed login attempts reaches 3 * number of total users in the last three (3) hours, the database triggers a FailedLoginWarning event. Failed login attempts could be due to a user entering an invalid username or password, or due to a connection timeout. The event is triggered when the failed login attempts threshold is exceeded within the monitored time period (the last three hours).
InstanceRelocateBegin	If an Autonomous Database is relocated to another Exadata infrastructure due to server maintenance, hardware refresh, a hardware issue, or as part of a resource scale up, the InstanceRelocateBegin event is triggered at the start of the relocation process.
InstanceRelocateEnd	If an Autonomous Database is relocated to another Exadata infrastructure due to server maintenance, hardware refresh, a hardware issue, or as part of a resource scale up, the InstanceRelocateEnd event is triggered at the end of the relocation process.
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.

Information Events on Autonomous Database

Information events 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. Information events are also available to provide details for some operations on Autonomous Database, such as when a workload capture or operator access is initiated.

The times shown with information 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).
InactiveConnectionsDetected	This event is generated when the number of inactive database connections detected is above a certain ratio compared to all database connections for the Autonomous Database instance. Subscribing to this event can help you keep track of unused connections. This event is generated once per day, when the following is true: The number of inactive connections, where the elapsed time for the inactive connection is greater than 24 hours, is great than 10% of the total number of connections in any state. For this calculation, inactive connections are connections where the status is "INACTIVE". Use the following query to report detailed information on sessions that have been inactive for more than 24 hours: SELECT sid, serial#, last_call_et FROM v$session WHERE status = 'INACTIVE' AND last_call_et > 60 * 60 *24;
Long term backup ended	This event is triggered when a long term backup completes.
Long term backup schedule disabled	This event is triggered when a long term backup schedule is disabled.
Long term backup schedule enabled / updated	This event is triggered when a long term backup schedule is either enabled or updated.
Long term backup started	This event is triggered when a long term backup starts.
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. When the Java version will be updated, the event description field indicates this with the following: This maintenance involves Java version update, please expect down time of Java service during this maintenance window.
OperatorAccess	This event is triggered when operator access is detected for the database. You can query the access details from the DBA_OPERATOR_ACCESS view with the request ID provided in the event description. The OperatorAccess event is generated once every 24 hours.
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. When the Java version will be updated, the event description field indicates this with the following message: This maintenance involves Java version update, please expect down time of Java service during this maintenance window.
WorkloadCaptureBegin	This event is triggered when a workload capture is initiated.
WorkloadCaptureEnd	This event is triggered when a workload capture completes successfully. This generates a pre-authenticated (PAR) URL to download the capture reports. This URL is contained in the captureDownloadURL field of the event and is valid for 7 days from the date of generation.
WorkloadReplayBegin	This event is triggered when a workload replay is initiated.
WorkloadReplayEnd	This event is triggered when a workload replay completes successfully. This generates a pre-authenticated (PAR) URL to download the replay reports. This URL is contained in the replayDownloadURL field of the event and is valid for 7 days from the date of generation.

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.

Get Notified of Autonomous Database Events

Using Oracle Cloud Infrastructure Events you can subscribe to Autonomous Database events individually or in two categories, Critical and Information events.

Note:

When you subscribe to an event category, either Critical or Information, you are notified when any events in the category occur. For example, to get notified when the database goes down, subscribe to the Autonomous Database Critical event type.

If you want to subscribe to Critical events, then create an event rule using the Autonomous Database - Critical event type. Likewise, if you want to be notified of Information events then create an event rule using the Autonomous Database - Information event type.

See About Events Based Notification and Automation on Autonomous Database for information on Critical and Information events.

See Getting Started with Events for information on using Oracle Cloud Infrastructure Events, creating event rules, and configuring actions for notifications.