Service Level Objectives (SLOs)
Describes the Service Level Objectives (SLOs) for Oracle Autonomous Database Serverless.
- Recovery Time Objective and Recovery Point Objective
Oracle Autonomous Database Serverless is engineered to return an application online following an unplanned outage or a planned maintenance activity within single-digit seconds. - Built-In Tool Availability
Oracle will use commercially reasonable efforts to have the following tools with a Monthly Uptime Percentage (Availability) objective as defined below, during the service commitment of a calendar month. - Zero-Regression Service Level Objective
Oracle Autonomous Database Serverless automatically applies patches on your database. Oracle provides a service level objective of zero regressions in your production database due to these patches.
Parent topic: Overview
Recovery Time Objective and Recovery Point Objective
Oracle Autonomous Database Serverless is engineered to return an application online following an unplanned outage or a planned maintenance activity within single-digit seconds.
The following table outlines the target Recovery Time Objective (RTO) SLOs for different failure events.
| Event | Recovery Time Objective (RTO) Service Level Objective | Recovery Point Objective (RPO) Service Level Objective, Maximum Possible Data Loss |
|---|---|---|
|
Events requiring failover to a standby database when Autonomous Data Guard is enabled, such as:
|
With an Autonomous Data Guard standby: Local Standby Database: two (2) minutes Cross-Region Standby Database: fifteen (15) minutes See Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for more information. |
Local Standby Database: The maximum possible data loss objective is < 10 seconds Cross-Region Standby Database: The maximum possible data loss objective is 1 minute |
|
Events requiring failover to a backup copy or restoring from a backup (when there is not an Autonomous Data Guard standby) such as:
|
With Backup-Based Disaster Recovery, based on the size of the database: Local backup copy: 1 hour + (1 hour per 5 TB) Cross-Region backup copy: 1 hour + (1 hour per 5 TB) For example, a 5 TB database has a Recovery Time Objective (RTO) of up to 2 hours. See Backup-Based Disaster Recovery Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for more information. |
Local backup copy: The maximum possible data loss objective is < 10 seconds Cross-Region backup copy: The maximum possible data loss objective is 1 minute |
Parent topic: Service Level Objectives (SLOs)
Built-In Tool Availability
Oracle will use commercially reasonable efforts to have the following tools with a Monthly Uptime Percentage (Availability) objective as defined below, during the service commitment of a calendar month.
| Oracle Autonomous Database Built-in Tool | Availability Service Level Objective |
|---|---|
| Oracle REST Data Services (ORDS) | 99.95% |
| Oracle APEX (on Autonomous Database) | 99.95% |
| Database Actions | 99.95% |
| Graph Studio | 99.95% |
Oracle Machine Learning:
|
99.95% |
| Data Transforms | 99.95% |
The following terms apply to the Availability Service Level Objective for the Oracle Autonomous Database Built-in Tools listed in this table:
-
“HTTP Error Rate” applies separately to each Database Built-in Tool and means the percentage value corresponds to: (i) the total number of failed HTTP calls made to the applicable tool with a status of “Bad Gateway” or “Service Unavailable” in a minute period during a calendar month, divided by (ii) the total number of HTTP calls made to the tool in a minute period.
-
“Monthly Uptime Percentage” is calculated by subtracting from 100%, the average of the HTTP Error Rate for each minute period during the applicable calendar month.
| Oracle Autonomous Database Built-in Tool | Availability Service Level Objective |
|---|---|
| Oracle Database API for MongoDB | 99.95% |
The following terms apply to the Availability Service Level Objective for Oracle Database API for MongoDB:
-
A "Connection through Oracle Database API for MongoDB" is a direct connection established from any tool or application to the Cloud Service using Oracle Database API for MongoDB.
-
“Monthly Uptime Percentage” is calculated by subtracting from 100%, the percentage of minutes during the calendar month in which the applicable Cloud Service was "Unavailable".
-
“Unavailable” means a minute period when: (i) no connection through Oracle Database API for MongoDB is or can be established and (ii) all continuous attempts, at least five, to establish such a connection fail.
Parent topic: Service Level Objectives (SLOs)
Zero-Regression Service Level Objective
Oracle Autonomous Database Serverless automatically applies patches on your database. Oracle provides a service level objective of zero regressions in your production database due to these patches.
Oracle Autonomous Database Serverless automatically applies patches containing bug and security fixes during the maintenance windows announced on your database console. When you provision your test or pre-prod database using the Early patch level option, you can test the patches on these instances before the patches are applied to your production database. If you see issues in your test or pre-prod database, you can file service requests to get the issues addressed before the patch is applied to your production database.
Oracle provides a service level objective of zero regressions in your production database. "Regression" in this document is described as issues introduced by patches or updates to the Autonomous Database performed during the maintenance window announced on your database console.
After a patch is applied to your database on the Early patch level, if you find and report an issue on that database through a service request, Oracle will use commercially reasonable efforts to address the problem so that the same issue does not occur in your production database.
See Set the Patch Level for more information.
Parent topic: Service Level Objectives (SLOs)