Oracle Cloud Infrastructure Documentation

Overview of Autonomous Database Dedicated Deployments

This topic describes the database architecture, features, and user roles of Autonomous Database dedicated deployments. For a general overview of Autonomous Databases that covers the basics common to both deployment options, see Overview of Autonomous Database.

Dedicated Deployment Database Architecture

Autonomous Databases with dedicated deployment have a three-level database architecture model that makes use of Oracle multitenant database architecture.

Resource types

Each level of the architecture model corresponds to one of the following resources types:

  • An Autonomous Exadata Infrastructure resource, a hardware rack which includes compute nodes and storage servers, tied together by a high-speed, low-latency InfiniBand network and intelligent Exadata software. With dedicated deployment, you have exclusive use of the Exadata infrastructure and hardware on which your Autonomous Transaction Processing databases run.

    For a list of the hardware and Oracle Cloud resource characteristics of Autonomous Exadata Infrastructure resources, see Characteristics of Autonomous Exadata Infrastructure Resources.

  • An Autonomous Container Database, which provides a container for multiple user databases. This resource is sometimes referred to as a CDB, and is functionally equivalent to the multitenant container databases found in Oracle 12c and higher databases.

    Multitenant architecture offers many advantages over non-CDB architecture. For example, it does the following:

    • Allows you to easily manage multiple individual user databases
    • Makes more efficient use of database hardware, as individual databases may use only a fraction of the server hardware capacity
    • Allows for easier and more rapid movement of data and code
    • Allows for easier testing, as development databases can be housed within the same container as production databases
    • Allows for the separation of duties between database administrators, who manage only the individual Autonomous Database instances to which they are granted privileges, and fleet managers, who manage infrastructure resources and container databases.
  • An Autonomous Database. You can create multiple Autonomous Databases within the same container database. This level of the database architecture is analogous to the pluggable databases (PDBs) found in non-Autonomous Exadata systems. Your Autonomous Database can be configured for either transaction processing or data warehouse workloads.

Deployment Order

You must create the dedicated deployment resources in the following order:

  1. Autonomous Exadata Infrastructure. See Creating an Autonomous Exadata Infrastructure Resource for more information.
  2. Autonomous Container Database. See Creating an Autonomous Container Database for more information.
  3. Autonomous Database. See Creating an Autonomous Database for more information.

Related Resources

Related resources and prerequisites include:

  • A Virtual Cloud Network (VCN) and a Subnet, which you create using Oracle Cloud Infrastructure's Networking service. You must have at least one VCN and one subnet available to provision an Autonomous Database with dedicated deployment.

    For more information, see the following topics:

  • Autonomous Backups, created for you automatically by the Autonomous Database service. You do not have to provision storage for your backups. Backups are stored in Object Storage that is managed by Oracle Cloud Infrastructure's Database service. Note that automatic backups incur Object Storage usage costs. By default, backups are stored for 60 days. Using the Console, you can choose to change the retention period to 7, 15, or 30 days.
  • Manual Backups. Optionally, you can configure Autonomous Database to create on-demand manual backups. See Setting Up a Bucket to Store Manual Backups and Backing Up an Autonomous Database Manually for more information on manual backups. Manual backups are subject to the retention policy you have in place for the Autonomous Container Database. By default, manual backups are stored for 60 days.

User Roles

Your organization may choose to split the administration of the Autonomous Database with dedicated deployment into the following roles:

  • Fleet Administrator. Fleet administrators create, monitor and manage Autonomous Exadata Infrastructure and Autonomous Container Database resources. A fleet administrator must have permissions for using the networking resources required by the dedicated deployment, and permissions to manage the infrastructure and container database resources.

    See Fleet Administrator’s Guide to Oracle Autonomous Transaction Processing Dedicated Deployments for a complete overview of the fleet administrator role.

  • Database Administrator. Database administrators create, monitor and manage Autonomous Databases. They also create and manage users within the database. Database administrators must have permissions for using container databases, for managing Autonomous Transaction Processing databases and backups, and for using the related networking resources. For manual backups, they must have permissions to use the designated Object Storage bucket. At the time of provisioning an Autonomous Database, the administrator provides user credentials for the automatically created ADMIN account, which provides administrative rights to the new database.

    See Using Oracle Autonomous Transaction Processing Dedicated Deployments for a complete overview of the database administrator role.

  • Database User. Database users are the developers who write applications that connect to and use an Autonomous Database to store and access the data. Database users do not need Oracle Cloud Infrastructure accounts. They gain network connectivity to and connection authorization information for the database from the database administrator.

CPU Provisioning, CPU Scaling, and Storage Scaling

Autonomous Database with dedicated deployment allows for the over-subscription of CPU cores when provisioning databases. This means that for a given infrastructure resource, the sum of all CPU cores provisioned to Autonomous Databases can exceed the number of CPU cores on the Exadata rack. This approach allows for better CPU core utilization. Note that if all databases are heavily loaded at the same time, there will be some contention for CPU resources, and degraded performance.

Additionally, you can scale the CPU count and the storage capacity of the database at any time without impacting availability or performance.

Overview of Dedicated Deployment Maintenance

Autonomous Database dedicated deployment systems have separate regularly scheduled maintenance runs for both Autonomous Exadata Infrastructure resources and Autonomous Container Databases. You can choose to set the scheduling for your maintenance runs, or let the system handle maintenance scheduling. You can view the maintenance history for infrastructure instances and container databases in the Oracle Cloud Infrastructure Console.


Oracle recommends that you define the acceptable maintenance times for your Autonomous Exadata Infrastructure resources and Autonomous Container Databases. Doing so will prevent maintenance runs from occurring at times that would be disruptive to regular database operations.

Autonomous Exadata Infrastructure Maintenance

Infrastructure maintenance takes place at least once each quarter and is mandatory. You can schedule the time your infrastructure maintenance will begin. Infrastructure maintenance runs are for infrastructure patching (including patching of the Exadata grid infrastructure code and operating systems updates), and do not include database patching. Oracle will notify you in the weeks leading up to the quarterly infrastructure patching date about the upcoming maintenance. You can also view scheduled maintenance runs in the Oracle Cloud Infrastructure console. The following tasks explain how to view scheduled and past maintenance updates, and to edit the maintenance schedule for an infrastructure instance:

You can use the GetMaintenanceRun, ListMaintenanceRun, and UpdateAutonomousExadataInfrastructure API operations to view details about scheduled and past maintenance updates, and to update the maintenance schedule of your infrastructure instance.

Autonomous Container Database Maintenance

Container database maintenance takes place at the time of the quarterly infrastructure maintenance run. Container database maintenance includes Oracle Database software patches. Autonomous Database offers two CDB maintenance type choices:

  • Release Update (RU): Autonomous Database installs only the most current release update.
  • Release Update Revision (RUR): Autonomous Database installs the release update plus additional fixes.

The following tasks explain how to view and edit maintenance update information for Autonomous Container Databases:

Use the UpdateAutonomousContainerDatabase API operation to change the patching type for an Autonomous Container Database. Use the ListMaintenanceRun API operation to see past maintenance update information. Use the UpdateMaintenanceRun API operations to skip a container database maintenance update. You can skip maintenance runs for up to 2 consecutive quarters if needed.

Using the Oracle Cloud Infrastructure Console to Manage Dedicated Deployments

For information on provisioning, managing, and backing up dedicated deployments in the Oracle Cloud Infrastructure Console, see the following topics:

For Fleet Administrators

For Database Administrators

Additional Information

For known issues, see Known Issues for Oracle Autonomous Transaction Processing Dedicated Deployments.