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.

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.

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.

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.

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.

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.

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.

Provides a message that the Autonomous Database user password is expiring within the specified grace period (default 30 days) or has already expired.

• If an Autonomous Database user password is within the specified grace period of being unusable, you receive a warning indicating the date when the password can no longer be used.

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

The DatabaseUserPasswordWarning event is generated once per day.

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).

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.

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.

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.

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 or begins to apply an Oracle APEX Patch Set Bundle.

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 or completes the installation of an Oracle APEX Patch Set Bundle.

AutomaticRefreshEnd

This event is generated when the scheduled Automatic Refresh completes.

See Edit Automatic Refresh Policy for Refreshable Clone for more information.

AutomaticRefreshFailed

This event is generated when the scheduled Automatic Refresh fails.

See Edit Automatic Refresh Policy for Refreshable Clone for more information.

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;

This event is triggered when a long term backup completes.

This event is triggered when a long term backup schedule is disabled.

This event is triggered when a long term backup schedule is either enabled or updated.

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).

This event is also triggered when the maintenance starts for a local Autonomous Data Guard standby.

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).

This event is also triggered when the maintenance ends for a local Autonomous Data Guard standby.

NewMaintenanceSchedule

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

This event is also triggered when the maintenance date is updated and the new date is shown for a local Autonomous Data Guard standby.

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.

NetworkUsageInbound

This event is triggered when the average incoming network traffic to your Autonomous Database for TCP or HTTP database connections in the last 24 hours has exceeded 50% of the average incoming traffic observed a day before.

When the trigger conditions for this event are met, the NetworkUsageInbound event is generated once per day.

NetworkUsageOutbound

This event is triggered when the average outgoing network traffic from your Autonomous Database for TCP or HTTP database connections in the last 24 hours has exceeded 50% of the average outgoing traffic observed a day before.

When the trigger conditions for this event are met, the NetworkUsageOutbound event is generated once per day.

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.

QueryPerformanceDegradationDetected

This event is triggered when the average elapsed time of a query has exceeded ten times its average elapsed time over the past seven (7) days.

The QueryPerformanceDegradationDetected event description field indicates the potential cause of a query performance degradation. For example, with a message such as:

Query performance slow down detected for SQL ID 9x25vyx9ujnn8. 
This could potentially be due to a recent compute scale down performed on this Autonomous Database. 
You might need to scale up your instance's compute allocation to address this performance degradation.

When the trigger conditions for this event are met, the QueryPerformanceDegradationDetected event is generated at most once per day.

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.

This event is also triggered when a local Autonomous Data Guard standby is 24 hours from a scheduled maintenance and again when the local Autonomous Data Guard standby 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.

This event is triggered when a workload capture is initiated.

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.

This event is triggered when a workload replay is initiated.

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.

See Critical Events on Autonomous Database for more information.

This event is emitted 48 hours prior to database stop.

This event is emitted 48 hours prior to database termination.

See Information Events on Autonomous Database for more information.

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.)

The "Manual Refresh" events are used for Autonomous Database refreshable clones.

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.