Use Autonomous AI Database Events

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

You can use Oracle Cloud Infrastructure Events to subscribe to and be notified of Autonomous AI 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 AI Database
  You can subscribe to Oracle Cloud Infrastructure Events.
• Critical Events on Autonomous AI Database
  Critical events on Autonomous AI Database are issues that cause disruption to the database.
• Information Events on Autonomous AI Database
  Information events provide important details about database lifecycle events, workload capture and reply events, and some other non-critical events on Autonomous AI Database.
• Autonomous AI Database Lifecycle Events
  Provides a list of Autonomous AI Database lifecycle events.
• Get Notified of Autonomous AI Database Events
  Using Oracle Cloud Infrastructure Events you can subscribe to Autonomous AI Database events individually or in two categories, Critical and Information events.

About Events Based Notification and Automation on Autonomous AI Database

You can subscribe to Oracle Cloud Infrastructure Events.

An event could be a resource life cycle state change or a system event impacting a resource. For example, an event is emitted on Autonomous AI Database when maintenance begins and ends. Subscribing to events allows you to receive notifications or to perform other types of automation for events.

You can subscribe to Autonomous AI Database events as follows:

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

• Lifecycle Management Events. See Autonomous AI Database Lifecycle Events for the list of Autonomous AI Database events.

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

Critical events and Information events include an event category attribute (in the eventCategory field). Optionally you can subscribe to events and add an event category to receive notifications about events in a category, or to perform other types of automation for events by event type and event category.

The event categories are:

• Incident: Database incident events
• Maintenance: Database maintenance events
• Performance: Database performance events
• Security: Database security events
• Other: Other events

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

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

Critical Events on Autonomous AI Database

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

Event	Event Category	Description
AdminPasswordWarning	Security	Provides a message that the Autonomous AI 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 AI Database reports an event that specifies that the ADMIN user password has expired and must be reset.
AutomaticFailoverBegin	Incident	When an automatic failover begins for the Autonomous AI 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	Incident	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	Incident	The Autonomous AI 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	Incident	The database is recovered from the down state, meaning the Autonomous AI 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	Incident	The Autonomous AI 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 AI Database instance is not able to reach the Oracle Cloud Infrastructure Vault.
DatabaseInaccessibleEnd	Incident	If the Autonomous AI 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.
DatabaseUserPasswordWarning	Security	Provides a message that the Autonomous AI Database user password is expiring within the specified grace period (default 30 days) or has already expired. If an Autonomous AI 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 AI Database user password expires and is no longer usable, Autonomous AI Database reports an event that specifies that the password has expired and must be reset. The DatabaseUserPasswordWarning event is generated once per day.
FailedLoginWarning	Security	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	Incident	If an Autonomous AI 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	Incident	If an Autonomous AI 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.
ScheduledUpgradeBegin	Other	When a scheduled upgrade begins for the Autonomous AI Database and the database is unavailable a ScheduledUpgradeBegin event is generated.
ScheduledUpgradeEnd	Other	When a scheduled upgrade ends for the Autonomous AI Database and the database is now available a ScheduledUpgradeEnd event is generated.
ScheduledUpgradeFailed	Other	When a scheduled upgrade fails for the Autonomous AI Database and the database is now available a ScheduledUpgradeFailed event is generated.
WalletExpirationWarning	Security	This event is generated when Autonomous AI 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 AI Database - Critical to specify critical events in Event rules.

Information Events on Autonomous AI Database

Information events provide important details about database lifecycle events, workload capture and reply events, and some other non-critical events on Autonomous AI Database.

The times shown with information events are in UTC.

Event	Event Category	Description
AJDNonJsonStorageExceeded	Performance	This event is generated when an Autonomous AI 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 AI JSON Database to Autonomous AI Transaction Processing. See Promote to Autonomous Transaction Processing for more information.
APEXUpgradeAvailable	Incident	This event is generated when you are using Oracle APEX and a new release becomes available.
APEXUpgradeBegin	Incident	This event is generated when you are using Oracle APEX and your Autonomous AI Database instance begins an upgrade to a new Oracle APEX release or begins to apply an Oracle APEX Patch Set Bundle.
APEXUpgradeEnd	Incident	This event is generated when you are using Oracle APEX and your Autonomous AI Database instance completes an upgrade to a new Oracle APEX release or completes the installation of an Oracle APEX Patch Set Bundle.
AutomaticRefreshEnd	Incident	This event is generated when the scheduled Automatic Refresh completes. See Edit Automatic Refresh Policy for Refreshable Clone for more information.
AutomaticRefreshFailed	Incident	This event is generated when the scheduled Automatic Refresh fails. See Edit Automatic Refresh Policy for Refreshable Clone for more information.
DatabaseConnection	Security	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	Security	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 AI 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;
LongPendingTransaction	Incident	This event is generated when a transaction is open for longer than 24 hours. Only one event is generated per transaction. The generated event includes the transaction id, address, and session address.
MaintenanceBegin	Maintenance	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	Maintenance	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	Maintenance	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	Security	This event is triggered when the average incoming network traffic to your Autonomous AI 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	Security	This event is triggered when the average outgoing network traffic from your Autonomous AI 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.
OperatorAccess	Other	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	Performance	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 AI 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.
ResourceUtilizationWarning	Performance	This event is triggered for the following metrics, when certain thresholds are exceeded: CPU: When the number of waiting sessions in your Autonomous AI Database exceeds 20% of your compute allocation. Storage: When storage auto scaling is disabled for your database and the allocated storage exceeds 80% of the provisioned storage. When storage auto scaling is enabled for your database and the allocated storage exceeds 80% of the provisioned storage, which is up to three times (3X) of the base storage. Sessions: When the number of concurrent sessions in your Autonomous AI Database has exceeded 80% of the session limit. For the CPU and Sessions metrics, the event is only eligible to be generated when: Auto scaling is enabled for your Autonomous AI Database and the ECPU count is greater than 4. Auto scaling is disabled for your Autonomous AI Database and the ECPU count is equal to or greater than 2. When the trigger conditions for this event are met, the ResourceUtilizationWarning event is generated once per hour. Note: The ResourceUtilizationWarning event is not generated when: The database uses the OCPU compute model. The database is an Autonomous AI Database for Developers. An Always Free Autonomous AI Database.
ScheduledMaintenanceWarning	Maintenance	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.
SQLParseErrorWarning	Incident	If a SQL parse error occurs several times in a certain time window, for example 200 times or more in an hour, this generates "Too Many Parse Errors" entries in the alert log. The SQLParseErrorWarning event is triggered when there is a new entry in the alert log, indicating that a SQL statement has too many parse errors. For example, when an invalid query runs 200 times in less than an hour, this triggers the SQLParseErrorWarning event. This event is generated at most once per day. This means there can be a delay of up to 24 hours before the event is generated.
UnplannedMaintenanceBegin	Maintenance	This event is generated when an instance requires an unplanned maintenance due to a critical security fix, a regression, or a failure during planned maintenance. This event informs you when the maintenance required for urgent and unplanned situations is initiated.
UnplannedMaintenanceEnd	Maintenance	This event is generated when an instance requires an unplanned maintenance due to a critical security fix, a regression, or a failure during planned maintenance. This event informs you when the maintenance required for urgent and unplanned situations is completed successfully.
WorkloadCaptureBegin	Incident	This event is triggered when a workload capture is initiated.
WorkloadCaptureEnd	Incident	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	Incident	This event is triggered when a workload replay is initiated.
WorkloadReplayEnd	Incident	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 AI 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.

Autonomous AI Database Lifecycle Events

Provides a list of Autonomous AI Database lifecycle events.

Friendly Name	Event Type
Autonomous AI Database - Access Control Lists Update Begin	com.oraclecloud.databaseservice.updateautonomousdatabaseacl.begin
Autonomous AI Database - Access Control Lists Update End	com.oraclecloud.databaseservice.updateautonomousdatabaseacl.end
Autonomous AI Database - Auto Scaling Disabled	com.oraclecloud.databaseservice.autonomousdatabaseautoscaledisabled
Autonomous AI Database - Auto Scaling Enabled	com.oraclecloud.databaseservice.autonomousdatabaseautoscaleenabled
Autonomous AI Database - Automatic Backup Begin	com.oraclecloud.databaseservice.automaticbackupautonomousdatabase.begin
Autonomous AI Database - Automatic Backup End	com.oraclecloud.databaseservice.automaticbackupautonomousdatabase.end
Autonomous AI Database - Change Compartment Begin	com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.begin
Autonomous AI Database - Change Compartment End	com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.end
Autonomous AI Database - Change Database Name Begin	com.oraclecloud.databaseservice.changeautonomousdatabasename.begin
Autonomous AI Database - Change Database Name End	com.oraclecloud.databaseservice.changeautonomousdatabasename.end
Autonomous AI Database - Create Backup Begin	com.oraclecloud.databaseservice.autonomous.database.backup.begin
Autonomous AI Database - Create Backup End	com.oraclecloud.databaseservice.autonomous.database.backup.end
Autonomous AI Database - Create Begin	com.oraclecloud.databaseservice.autonomous.database.instance.create.begin
Autonomous AI Database - Create End	com.oraclecloud.databaseservice.autonomous.database.instance.create.end
Autonomous AI Database - Critical See Critical Events on Autonomous AI Database for more information.	com.oraclecloud.databaseservice.autonomous.database.critical
Autonomous AI Database - Deregister Autonomous Database with Data Safe Begin	com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.begin
Autonomous AI Database - Deregister Autonomous Database with Data Safe End	com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.end
Autonomous AI Database - Disable Data Guard Begin	com.oraclecloud.databaseservice.disableautonomousdataguard.begin
Autonomous AI Database - Disable Data Guard End	com.oraclecloud.databaseservice.disableautonomousdataguard.end
Autonomous AI Database - Disconnect Refreshable Clone from Source Database Begin	com.oraclecloud.databaseservice.disconnectrefreshableautonomousdatabaseclonefromsource.begin
Autonomous AI Database - Disconnect Refreshable Clone from Source Database End	com.oraclecloud.databaseservice.disconnectrefreshableautonomousdatabaseclonefromsource.end
Autonomous AI Database - Enable Data Guard Begin	com.oraclecloud.databaseservice.enableautonomousdataguard.begin
Autonomous AI Database - Enable Data Guard End	com.oraclecloud.databaseservice.enableautonomousdataguard.end
Autonomous AI Database - Free Database Automatic Stop Reminder This event is emitted 48 hours prior to database stop.	com.oraclecloud.databaseservice.freeautonomousdatabasestopreminder
Autonomous AI Database - Free Database Automatically Stopped	com.oraclecloud.databaseservice.freeautonomousdatabasestopped
Autonomous AI Database - Free Database Automatic Termination Reminder. This event is emitted 48 hours prior to database termination.	com.oraclecloud.databaseservice.freeautonomousdatabaseterminationreminder
Autonomous AI Database - Free Database Automatically Terminated	com.oraclecloud.databaseservice.freeautonomousdatabaseterminated
Autonomous AI Database - Generate Wallet	com.oraclecloud.databaseservice.generateautonomousdatabasewallet
Autonomous AI Database - Information See Information Events on Autonomous AI Database for more information.	com.oraclecloud.databaseservice.autonomous.database.information
Autonomous AI Database - Long term backup ended This event is triggered when a long term backup completes.
Autonomous AI Database - Long term backup schedule disabled This event is triggered when a long term backup schedule is disabled.
Autonomous AI Database - Long term backup schedule enabled / updated This event is triggered when a long term backup schedule is either enabled or updated.
Autonomous AI Database - Long term backup started This event is triggered when a long term backup starts.
Autonomous AI Database - Manual Failover Begin	com.oraclecloud.databaseservice.failoverautonomousdatabase.begin
Autonomous AI 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 AI 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 AI Database - Manual Refresh Begin The "Manual Refresh" events are used for Autonomous AI Database refreshable clones.	com.oraclecloud.databaseservice.manualrefresh.begin
Autonomous AI Database - Manual Refresh End	com.oraclecloud.databaseservice.manualrefresh.end
Autonomous AI Database - Deregister Autonomous AI Database with Data Safe Begin	com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.begin
Autonomous AI Database - Deregister Autonomous AI Database with Data Safe End	com.oraclecloud.databaseservice.deregisterautonomousdatabasedatasafe.end
Autonomous AI Database - Register Autonomous AI Database with Data Safe Begin	com.oraclecloud.databaseservice.registerautonomousdatabasedatasafe.begin
Autonomous AI Database - Register Autonomous AI Database with Data Safe End	com.oraclecloud.databaseservice.registerautonomousdatabasedatasafe.end
Autonomous AI Database - Restart Begin	com.oraclecloud.databaseservice.restartautonomousdatabase.begin
Autonomous AI Database - Restart End	com.oraclecloud.databaseservice.restartautonomousdatabase.end
Autonomous AI Database - Restore Begin	com.oraclecloud.databaseservice.autonomous.database.restore.begin
Autonomous AI Database - Restore End	com.oraclecloud.databaseservice.autonomous.database.restore.end
Autonomous AI Database - Rotate Encryption Key Begin	com.oraclecloud.databaseservice.rotateautonomousdatabaseencryptionkey.begin
Autonomous AI Database - Rotate Encryption Key End	com.oraclecloud.databaseservice.rotateautonomousdatabaseencryptionkey.end
Autonomous AI Database - Start Begin	com.oraclecloud.databaseservice.startautonomousdatabase.begin
Autonomous AI Database - Start End	com.oraclecloud.databaseservice.startautonomousdatabase.end
Autonomous AI Database - Stop Begin	com.oraclecloud.databaseservice.stopautonomousdatabase.begin
Autonomous AI Database - Stop End	com.oraclecloud.databaseservice.stopautonomousdatabase.end
Autonomous AI Database - Switchover Begin	com.oraclecloud.databaseservice.switchoverautonomousdatabase.begin
Autonomous AI Database - Switchover End This event is emitted after switchover completes successfully or unsuccessfully. Unsuccessful switchovers may result in data loss. Check the Autonomous AI 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 AI Database - Terminate Begin	com.oraclecloud.databaseservice.deleteautonomousdatabase.begin
Autonomous AI Database - Terminate End	com.oraclecloud.databaseservice.deleteautonomousdatabase.end
Autonomous AI Database - Update Begin	com.oraclecloud.databaseservice.updateautonomousdatabase.begin
Autonomous AI Database - Update End	com.oraclecloud.databaseservice.updateautonomousdatabase.end
Autonomous AI Database - Update Open Mode Begin	com.oraclecloud.databaseservice.updateautonomousdatabaseopenmode.begin
Autonomous AI Database - Update Open Mode End	com.oraclecloud.databaseservice.updateautonomousdatabaseopenmode.end
Autonomous AI Database - Upgrade Database Version Begin	com.oraclecloud.databaseservice.upgradeautonomousdatabasedbversion.begin
Autonomous AI Database - Upgrade Database Version End	com.oraclecloud.databaseservice.upgradeautonomousdatabasedbversion.end

Get Notified of Autonomous AI Database Events

Using Oracle Cloud Infrastructure Events you can subscribe to Autonomous AI 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 AI 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 AI Database - Critical event type.

• To subscribe to Information events, create an event rule using the Autonomous AI 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:

1. On the Oracle Cloud Infrastructure Console click Observability & Management.
2. Under Events Service, click Rules.
3. To add a rule, click Create Rule.
4. On the Create Rule page, enter a Display Name and a Description.
5. Under Rule Conditions, enter a rule condition
   1. Enter the Condition: Event Type.
   2. Enter the Service Name: Database.
   3. Enter the Event Type, one of: Autonomous AI Database - Critical or Autonomous AI Database - Information.
6. Click + Another Condition.
7. Under Condition, select Attribute.
   1. Under Attribute Name, select eventName.
   2. Under Attribute Values, enter the event name. For example, enter AdminPasswordWarning.

      See Critical Events on Autonomous AI Database and Information Events on Autonomous AI Database for the list of event names.

   For example with these entries the Rule Logic area shows:

   MATCH event WHERE (
      eventType EQUALS ANY OF (
         com.oraclecloud.databaseservice.autonomous.database.critical
      )
      AND (
            eventName MATCHES ANY OF (
                AdminPasswordWarning
            )
      )
   )

8. In the Actions area, select the actions you want.
9. Click Create Rule.

Critical events and Information events include an event category attribute (in the eventCategory field). Optionally you can subscribe to events by event type and include an event category to receive notifications about events in that category, or to perform other types of automation for events.

The event categories are:

• Incident: Database incident events
• Maintenance: Database maintenance events
• Performance: Database performance events
• Security: Database security events
• Other: Other events

For example, if you want to subscribe Critical events with the event category Security, create an event rule as shown, and in Step 7, select the eventCategory attribute and enter a value.

The result would look like this:

MATCH event WHERE (
   eventType EQUALS ANY OF (
      com.oraclecloud.databaseservice.autonomous.database.critical
   )
   AND (
     eventCategory MATCHES ANY OF (
       Security
     )
   )
)

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