Oracle Cloud Infrastructure Documentation

Overview of Autonomous Database

Oracle Cloud Infrastructure's Autonomous Database is a fully managed, preconfigured database environment with two workload types available, Autonomous Transaction Processing and Autonomous Data Warehouse. You do not need to configure or manage any hardware, or install any software. After provisioning, you can scale the number of CPU cores or the storage capacity of the database at any time without impacting availability or performance. Autonomous Database handles creating the database, as well as the following maintenance tasks:

  • Backing up the database
  • Patching the database
  • Upgrading the database
  • Tuning the database

Available Workload Types

Autonomous Database offers two workload types:

  • The Autonomous Transaction Processing workload type configures the database for a transactional workload, with a bias towards high volumes of random data access.

    For a complete product overview of Autonomous Transaction Processing, see Autonomous Transaction Processing. For Autonomous Transaction Processing tutorials, see Quick Start tutorials.

  • The Autonomous Data Warehouse workload type configures the database for a decision support or data warehouse workload, with a bias towards large data scanning operations.

    For a complete product overview of Autonomous Data Warehouse, see Autonomous Data Warehouse. For Autonomous Data Warehouse tutorials, see Quick Start tutorials.

Autonomous Transaction Processing Deployment Types

For Autonomous Transaction Processing databases, you have the following deployment options:

  • Dedicated deployment.  Using the dedicated deployment option, you have exclusive use of the Exadata infrastructure and hardware. Dedicated deployment offers multitenant database architecture, allowing you to create and manage multiple Autonomous Databases within a single database system. For an overview of Autonomous Transaction Processing Dedicated Deployments, see Overview of Autonomous Transaction Processing Dedicated Deployments.
  • Serverless  deployment. With the serverless deployment option, you provision and manage only the Autonomous Transaction Processing database, while Oracle handles the infrastructure deployment and management tasks.

CPU Scaling

For serverless deployments, the auto scaling feature enables the system to automatically adjust the number of CPU cores as load demand fluctuates, allowing the system to use cores more efficiently. As demand increases, auto scaling gradually increases the number of cores, up to a maximum of three times the assigned number. Likewise, it gradually decreases cores as demand drops. You can also scale the database's assigned number of CPU cores up or down at any time. CPU scaling does not impact Autonomous Database availability or performance. Note the following points regarding the auto scaling feature:

  • The maximum number of cores that can be made available to a database remains 128, regardless of whether auto scaling is enabled or not. This means that database with a CPU core count of 64 could auto scale up to two times the assigned number of cores (2 x 64 = 128). A database with 42 cores (or fewer) could auto scale up to three times the assigned number (3 x 42 = 126).
  • Auto scaling can be enabled or disabled at any time.
  • The auto scaling status for a database (enabled or disabled) is displayed on the database details page.
  • You can view hourly snapshots of the database's actual CPU usage over the most recent 8 days. This information is available in the Service Console, in the Overview page graph "Number of OCPUs Allocated". For more information, see To view CPU allocation hourly snapshot data for an Autonomous Database.
  • For billing purposes, the Autonomous Database service determines the average CPU utilization per hour.

Storage Scaling

Autonomous Database allows you to scale the storage capacity of the database at any time without impacting availability or performance.

Availability

Oracle Cloud Infrastructure' s Autonomous Database is currently available in the following regions:

Region Name Region Location Region Key
ap-seoul-1 Asia-Pacific: Seoul, South Korea ICN
ap-tokyo-1 Asia-Pacific: Tokyo, Japan NRT
ca-toronto-1 Canada: Toronto YYZ
eu-frankfurt-1 Europe: Frankfurt, Germany FRA
uk-london-1 United Kingdom: London LHR
us-ashburn-1 United States: Ashburn, VA IAD
us-phoenix-1 United States: Phoenix, AZ PHX

Security Considerations

Autonomous Databases have public IP addresses and therefore are accessible to any client on the internet by default. Oracle recommends that you secure access to your database by using a service gateway or an access control list (ACL).

Service Gateway

Oracle Autonomous Database is one of the Oracle Cloud services that can be privately accessed through a service gateway within a virtual cloud network (VCN). This means you do not need a public IP or NAT to access your Autonomous Database instance from any of the cloud services within the Oracle Services Network. For example, if you have a Compute instance that uses a VCN with a service gateway, you can route traffic between your Compute instance and an Autonomous Database in the same region without the traffic going over the internet. For information on setting up a VCN service gateway and configuring it to access all supported Oracle Service Network services (which include Autonomous Database), see Access to Oracle Services: Service Gateway.

Access Control List (ACL)

An access control list provides additional protection for your Autonomous Database by allowing only the IP addresses in the list to connect to the database.

When you provision a new Autonomous Database, it does not have an initial ACL. You can use the Oracle Cloud Infrastructure Console, API, or CLI to create an ACL for the database by adding a minimum of one entry to the list. An entry can be a comma-separated list of CIDR blocks or public IP addresses. You can modify the list at any time. Removing all entries from the list makes the database accessible to all clients with the applicable credentials. See To manage the access control list of an Autonomous Database to learn how to create, update, or delete an ACL.

Important

If you are using a service gateway and you configure an access control list, you must add the CIDR range 240.0.0.0/4 to the ACL to enable clients accessing the database through the service gateway to connect to it.

Using the Oracle Cloud Infrastructure Console to Manage Autonomous Databases

For information on provisioning, managing, and backing up an Autonomous Database in the Oracle Cloud Infrastructure Console, see the following topics:

Additional Autonomous Database Product Information

Autonomous Transaction Processing

Hidden x-ref linking content. Do not remove! This topic has moved. Please update your bookmarks.

Hidden x-ref linking content. Do not remove! This topic has moved. Please update your bookmarks.