Create an Autonomous Database on Dedicated Exadata Infrastructure

You can create an Autonomous Database on Dedicated Exadata Infrastructure from the Oracle Cloud Infrastructure console.


In an Autonomous Data Guard setup, you can not create an Autonomous Database in an Autonomous Container Database (ACD) whose standby ACD is in a snapshot standby role.

Required IAM Policies

manage autonomous-databases

read autonomous-container-databases

Related Live Labs

For a "try it out" alternative that demonstrates these instructions, see Lab 1: Provisioning Databases in Oracle Autonomous Database Dedicated for Developers and Database Users Workshop.


  1. Go to Autonomous Database in the Oracle Cloud Infrastructure Console.
  2. If needed, switch to the region where you want to create the database.

    See Switching Regions for information on switching regions and working in multiple regions.

  3. In the side menu's list of Autonomous Database resource types, click Autonomous Database.
  4. Click Create Autonomous Database.
  5. Fill out the Create Autonomous Database page with the following information:
    Setting Description Notes


    Select a compartment to host the Autonomous Database.


    Display name

    Enter a user-friendly description or other information that helps you easily identify the Autonomous Database.

    Avoid entering confidential information.

    Database name

    Provide a name for the new Autonomous Database.

    Must consist of letters and numbers only. The maximum length is 30 characters.

    The same database name cannot be used for multiple Autonomous Databases in the same Autonomous Exadata VM Cluster.

    Workload type

    Choose Data Warehouse or Transaction Processing.

    Determines the configuration of the new Autonomous Database.

    JSON and APEX workload types are not supported on dedicated Exadata infrastructure.

    Deployment type

    Select Dedicated Infrastructure. APPLIES TO: Applicable Oracle Public Cloud only

    Autonomous Container Database

    Select an Autonomous Container Database in which to create the Autonomous Database.

    Click Change Compartment to select from a different compartment.

    Start by choosing whether you want a standard autonomous container database or an autonomous container database configured to use Autonomous Data Guard.

    Availability In an Autonomous Data Guard setup, you can not create an Autonomous Database in an Autonomous Container Database (ACD)  whose standby ACD is in a snapshot standby role.

    If you choose an autonomous container database configured to use Autonomous Data Guard, two databases of the CPU count and storage you select are created: one in a primary container database, and one (a synchronized copy) in a standby container database. For more information, see Manage Primary and Standby Databases in an Autonomous Data Guard Configuration .

    Suppose an Autonomous Container Database with a cross-region Autonomous Data Guard association has a switchover or failover, and its standby assumes the primary role. In this case, creating a Autonomous Database in such an Autonomous Container Database will fail because the replicated vault used by the standby is read-only.

    CPU count

    Select the number of CPUs for your database from the list of provisionable CPUs.

    The CPU type, that is, ECPU or OCPU is determined by the parent Autonomous Exadata VM Cluster's compute type. This value defaults to 4 ECPUs or 1 OCPU depending on the CPU type. Refer to Compute Models in Autonomous Database for more details.

    For databases that need 1 or more OCPUs or 2 or more ECPUs, you must specify the number of assigned CPUs as an integer. For example, you cannot assign 3.5 ECPUs to a database. The next available number of ECPUs above 3 is 4.

    You can also assign OCPU count from 0.1 to 0.9 in increments of 0.1 OCPUs for databases that do not need an entire OCPU. This allows you to overprovision CPU and run more databases on each infrastructure instance. Refer to CPU Overprovisioning for more details.

    Not Applicable CPU overprovisioning is not supported for Autonomous Databases that use ECPUs.

    CPU auto scaling

    Enable or disable CPU auto scaling, which permits Autonomous Database to automatically use up to three times as many CPUs as specified by CPU Count as the workload on the database increases.


    Storage (GB)

    Specify the storage to allocate to your database in terabytes (GB), with a minimum value of 32 GB.

    The default values are 1024 GB for Autonomous Data Warehouse and 32 GB for the Autonomous Transaction Processing workloads.


    Denotes the database's username. This is a read-only value.



    Set the password for the Admin database user in your new database.

    The password must meet the strong password complexity criteria based on Oracle Cloud security standards. For more information on the password complexity rules, see Create Database Users.

    Confirm password

    Re-enter the password for confirmation.


    Access Control

    Optionally, click Modify Access Control to configure network access by enabling database level access control, which is disabled by default.

    Clicking Modify Access Control opens the Edit Access Control List dialog.

    Database-level access control

    To configure network access by creating an access control list (ACL), select Enable database-level access control, and click + Access Control Rule on the Edit Access Control List dialog.

    Depending on the types of addresses in your list, select one of the following options from the IP notation type drop-down selector:
    • IP Address: Specify individual IP addresses. You can use commas to separate multiple IP addresses.
    • CIDR Block: Specify ranges of public IP addresses using CIDR notation. You can use commas to separate multiple values.

    An ACL provides additional protection to your Autonomous Database by allowing only the client with specific IP addresses to connect to the database. See Restrict Access Using a Network Access Control List for details.

    Standby database access control

    If the parent Autonomous Container Database uses Autonomous Data Guard, you can define access control for the standby database also.

    Depending on your preference, select one of the following options for Standby database access control:
    • Choose Same as primary database to apply the ACL that you already defined for the primary database to the standby database as well. This is the default selection.
    • Choose Define standby database access control to define a separate ACL for the standby database. By default, the standby database ACL is initialized with the same values as the primary database ACL. Add or modify the entries as needed.
    By default, the ACL defined for the primary database applies to the standby database also.

    Show/hide advanced options

    By default, advanced options are hidden. Click Show advanced options to display them.


    Advanced options: Encryption key

    The encryption key settings are inherited from the parent Autonomous Container Database.  

    Advanced options: Management

    Choose a Character Set and National Character Set from the drop-down list.

    Refer to Character Set Selection for Dedicated Autonomous Database for more details.

    Advanced options: Database In-memory

    Optionally, select Enable database In-memory and adjust the percentage of System Global Area (SGA) to allocate.

    Please see Database In-Memory for the requirements and guidelines to use this feature with Autonomous Database.

    If required, you can also disable Database In-Memory from the Oracle Cloud Infrastructure (OCI) console. See Enable or Disable Database In-Memory for instructions.

    Advanced options: Tags

    If you want to use tags, add tags by selecting a Tag Namespace, Tag Key, and Tag Value.

    Tagging is a metadata system that allows you to organize and track resources within your tenancy. See Tagging Dedicated Autonomous Database Cloud Resources.

  6. Optionally, you can save the resource configuration as a stack by clicking Save as Stack. You can then use the stack to create the resource through the Resource Manager service.
    Enter the following details on the Save as Stack dialog, and click Save.
    • Name: Optionally, enter a name for the stack.
    • Description: Optionally, enter a description for this stack.
    • Save in compartment: Select a compartment where this Stack will reside.
    • Tag namespace, Tag key, and Tag value: Optionally, apply tags to the stack.

    For requirements and recommendations for Terraform configurations used with Resource Manager, see Terraform Configurations for Resource Manager. To provision the resources defined in your stack, apply the configuration.

  7. Click Create Autonomous Database.

Your display shows Provisioning until the new Autonomous Database is available.


When you create an Autonomous Database, CPU billing is initiated, billed by the second with a minimum usage period of one minute.