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.
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.
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 life cycle state change or a system event
impacting a resource. For example, an event is emitted on Autonomous 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 Database events as follows:
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.
Critical events on Autonomous Database are issues that cause disruption to the database.
Event
Event Category
Description
AdminPasswordWarning
Security
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
Incident
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
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 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 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 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
Incident
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.
DatabaseUserPasswordWarning
Security
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.
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 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 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
Security
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 provide important details about database lifecycle
events, workload capture and reply events, and some other non-critical events on Autonomous Database.
The times shown with information events are in UTC.
Event
Event Category
Description
AJDNonJsonStorageExceeded
Performance
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
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 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 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.
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 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 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 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 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
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.
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 Database - Information
to specify information events in Event rules.
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.)
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.
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 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:
On the Oracle Cloud
Infrastructure Console click Observability &
Management.
Under Events Service, click
Rules.
To add a rule, click Create Rule.
On the Create Rule page, enter a Display Name and a Description.
Under Rule Conditions, enter a rule condition
Enter the Condition: Event Type.
Enter the Service Name: Database.
Enter the Event Type, one of: Autonomous Database -
Critical or Autonomous Database -
Information.
Click + Another Condition.
Under Condition, select Attribute.
Under Attribute Name, select
eventName.
Under Attribute Values, enter the event name. For example, enter
AdminPasswordWarning.
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
)
)
)
In the Actions area, select the actions you
want.
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.