Use Autonomous Database Events
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 database lifecycle events, workload capture and reply events, and some other non-critical events on Autonomous Database. - Autonomous Database Event Types
Provides a list of Autonomous Database events. - 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.
Parent topic: Manage the Service
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. 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 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.
Parent topic: Use Autonomous Database Events
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.
|
AutomaticFailoverBegin |
When an automatic failover begins for the Autonomous Database and the database is unavailable an 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 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
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
The following conditions do not trigger
If you are using Autonomous Data
Guard
and the primary database goes down, this triggers a
|
DatabaseInaccessibleBegin |
The Autonomous Database instance is using customer-managed keys and the database becomes inaccessible (state shows Inaccessible). The following conditions trigger
|
DatabaseInaccessibleEnd |
If the Autonomous Database instance recovers from the Inaccessible
state that generated a |
FailedLoginWarning |
If the number of failed login attempts reaches 3 *
number of total users in the last three (3) hours, the
database triggers a 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
|
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
|
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.
Parent topic: Use Autonomous Database Events
Information Events on Autonomous Database
The times shown with information events are in UTC.
Event | Description |
---|---|
|
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. |
|
This event is generated when you are using Oracle APEX and a new release becomes available. |
|
This event is generated when you are using Oracle APEX and your Autonomous Database instance begins an upgrade to a new Oracle APEX release or begins to apply an Oracle APEX Patch Set Bundle. |
|
This event is generated when you are using Oracle APEX and your Autonomous Database instance completes an upgrade to a new Oracle APEX release or completes the installation of an Oracle APEX Patch Set Bundle. |
|
This event is generated when the scheduled Automatic Refresh completes. |
|
This event is generated when the scheduled Automatic Refresh fails. |
|
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). |
|
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:
Use the following query to report detailed information on sessions that have been inactive for more than 24 hours:
|
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. |
|
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). |
|
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). |
|
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
|
OperatorAccess |
This event is triggered when operator access is detected for the database. You can query the access details from the The |
|
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
|
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 |
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 |
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.
Parent topic: Use Autonomous Database Events
Autonomous Database Event Types
Provides a list of Autonomous Database events.
Friendly Name | Event Type |
---|---|
Autonomous Database - Access Control Lists Update Begin |
com.oraclecloud.databaseservice.updateautonomousdatabaseacl.begin |
Autonomous Database - Access Control Lists Update End | com.oraclecloud.databaseservice.updateautonomousdatabaseacl.end |
Autonomous Database - Auto Scaling Disabled | com.oraclecloud.databaseservice.autonomousdatabaseautoscaledisabled |
Autonomous Database - Auto Scaling Enabled | com.oraclecloud.databaseservice.autonomousdatabaseautoscaleenabled |
Autonomous Database - Automatic Backup Begin | com.oraclecloud.databaseservice.automaticbackupautonomousdatabase.begin |
Autonomous Database - Automatic Backup End | com.oraclecloud.databaseservice.automaticbackupautonomousdatabase.end |
Autonomous Database - Change Compartment Begin | com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.begin |
Autonomous Database - Change Compartment End | com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.end |
Autonomous Database - Change Database Name Begin | com.oraclecloud.databaseservice.changeautonomousdatabasename.begin |
Autonomous Database - Change Database Name End | com.oraclecloud.databaseservice.changeautonomousdatabasename.end |
Autonomous Database - Create Backup Begin | com.oraclecloud.databaseservice.autonomous.database.backup.begin |
Autonomous Database - Create Backup End | com.oraclecloud.databaseservice.autonomous.database.backup.end |
Autonomous Database - Create Begin | com.oraclecloud.databaseservice.autonomous.database.instance.create.begin |
Autonomous Database - Create End | com.oraclecloud.databaseservice.autonomous.database.instance.create.end |
Autonomous Database - Critical
See Critical Events on Autonomous Database for more information. |
com.oraclecloud.databaseservice.autonomous.database.critical |
Autonomous Database - Deregister Autonomous Database with Data Safe Begin | com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.begin |
Autonomous Database - Deregister Autonomous Database with Data Safe End | com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.end |
Autonomous Database - Disable Data Guard Begin | com.oraclecloud.databaseservice.disableautonomousdataguard.begin |
Autonomous Database - Disable Data Guard End | com.oraclecloud.databaseservice.disableautonomousdataguard.end |
Autonomous Database - Disconnect Refreshable Clone from Source Database Begin | com.oraclecloud.databaseservice.disconnectrefreshableautonomousdatabaseclonefromsource.begin |
Autonomous Database - Disconnect Refreshable Clone from Source Database End | com.oraclecloud.databaseservice.disconnectrefreshableautonomousdatabaseclonefromsource.end |
Autonomous Database - Enable Data Guard Begin | com.oraclecloud.databaseservice.enableautonomousdataguard.begin |
Autonomous Database - Enable Data Guard End | com.oraclecloud.databaseservice.enableautonomousdataguard.end |
Autonomous Database - Free Database Automatic Stop
Reminder
This event is emitted 48 hours prior to database stop. |
com.oraclecloud.databaseservice.freeautonomousdatabasestopreminder |
Autonomous Database - Free Database Automatically Stopped | com.oraclecloud.databaseservice.freeautonomousdatabasestopped |
Autonomous Database - Free Database Automatic Termination
Reminder.
This event is emitted 48 hours prior to database termination. |
com.oraclecloud.databaseservice.freeautonomousdatabaseterminationreminder |
Autonomous Database - Free Database Automatically Terminated | com.oraclecloud.databaseservice.freeautonomousdatabaseterminated |
Autonomous Database - Generate Wallet | com.oraclecloud.databaseservice.generateautonomousdatabasewallet |
Autonomous Database - Information
See Information Events on Autonomous Database for more information. |
com.oraclecloud.databaseservice.autonomous.database.information |
Autonomous Database - Manual Failover Begin | com.oraclecloud.databaseservice.failoverautonomousdatabase.begin |
Autonomous Database - Manual Failover End
This event is emitted after failover completes successfully or unsuccessfully. Unsuccessful manual failovers may result in data loss. Check the Autonomous Database details page in the Oracle Cloud Infrastructure Console for additional information in the event of an unsuccessful manual failover.) |
com.oraclecloud.databaseservice.failoverautonomousdatabase.end |
Autonomous Database - Manual Refresh Begin
The "Manual Refresh" events are used for Autonomous Database refreshable clones. |
com.oraclecloud.databaseservice.manualrefresh.begin |
Autonomous Database - Manual Refresh End | com.oraclecloud.databaseservice.manualrefresh.end |
Autonomous Database - Deregister Autonomous Database with Data Safe Begin | com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.begin |
Autonomous Database - Deregister Autonomous Database with Data Safe End | com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.end |
Autonomous Database - Register Autonomous Database with Data Safe Begin | com.oraclecloud.databaseservice.registerautonomousdatabasedatasafe.begin |
Autonomous Database - Register Autonomous Database with Data Safe End | com.oraclecloud.databaseservice.registerautonomousdatabasedatasafe.end |
Autonomous Database - Restart Begin | com.oraclecloud.databaseservice.restartautonomousdatabase.begin |
Autonomous Database - Restart End | com.oraclecloud.databaseservice.restartautonomousdatabase.end |
Autonomous Database - Restore Begin | com.oraclecloud.databaseservice.autonomous.database.restore.begin |
Autonomous Database - Restore End | com.oraclecloud.databaseservice.autonomous.database.restore.end |
Autonomous Database - Rotate Encryption Key Begin | com.oraclecloud.databaseservice.rotateautonomousdatabaseencryptionkey.begin |
Autonomous Database - Rotate Encryption Key End | com.oraclecloud.databaseservice.rotateautonomousdatabaseencryptionkey.end |
Autonomous Database - Start Begin | com.oraclecloud.databaseservice.startautonomousdatabase.begin |
Autonomous Database - Start End | com.oraclecloud.databaseservice.startautonomousdatabase.end |
Autonomous Database - Stop Begin | com.oraclecloud.databaseservice.stopautonomousdatabase.begin |
Autonomous Database - Stop End | com.oraclecloud.databaseservice.stopautonomousdatabase.end |
Autonomous Database - Switchover Begin | com.oraclecloud.databaseservice.switchoverautonomousdatabase.begin |
Autonomous Database - Switchover End
This event is emitted after switchover completes successfully or unsuccessfully. Unsuccessful switchovers may result in data loss. Check the Autonomous Database details page in the Oracle Cloud Infrastructure Console for additional information in the event of an unsuccessful switchover. |
com.oraclecloud.databaseservice.switchoverautonomousdatabase.end |
Autonomous Database - Terminate Begin | com.oraclecloud.databaseservice.deleteautonomousdatabase.begin |
Autonomous Database - Terminate End | com.oraclecloud.databaseservice.deleteautonomousdatabase.end |
Autonomous Database - Update Begin | com.oraclecloud.databaseservice.updateautonomousdatabase.begin |
Autonomous Database - Update End | com.oraclecloud.databaseservice.updateautonomousdatabase.end |
Autonomous Database - Update Open Mode Begin | com.oraclecloud.databaseservice.updateautonomousdatabaseopenmode.begin |
Autonomous Database - Update Open Mode End | com.oraclecloud.databaseservice.updateautonomousdatabaseopenmode.end |
Autonomous Database - Upgrade Database Version Begin | com.oraclecloud.databaseservice.upgradeautonomousdatabasedbversion.begin |
Autonomous Database - Upgrade Database Version End | com.oraclecloud.databaseservice.upgradeautonomousdatabasedbversion.end |
Parent topic: Use Autonomous Database Events
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.
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 or Information events:
-
To subscribe to Critical events, create an event rule using the Autonomous Database - Critical event type.
-
To subscribe to Information events, create an event rule using the Autonomous Database - Information event type.
If you want to subscribe to one or more individual Critical or
Information events, create an event rule and add conditions. For example, to
create an event rule that only applies for the
AdminPasswordWarning
Critical event, create a rule as
follows:
See Getting Started with Events for information on using Oracle Cloud Infrastructure Events, creating event rules, and for information on configuring actions for notifications.
Parent topic: Use Autonomous Database Events