Provision Autonomous Database

Follow these steps to provision a new Autonomous Database instance using the Oracle Cloud Infrastructure Console.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon next to Oracle Cloud.

  • From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  • Choose your region. See Switching Regions for information on switching regions and working in multiple regions.

  • Choose your Compartment. See Compartments for information on using and managing compartments.

On the Autonomous Databases page, perform the following steps:

  1. Click Create Autonomous Database.
  2. Provide basic information for the Autonomous Database.
    • Choose a compartment. See Compartments for information on using and managing compartments.

    • Display name Specify a user-friendly description or other information that helps you easily identify the resource. The display name does not have to be unique.


      After you create an Autonomous Database you cannot change the display name.
    • Database name Specify the database name; it 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 tenancy in the same region.

  3. Choose a workload type. Select the workload type for your database from the choices:
    • Data Warehouse

    • Transaction Processing

    • JSON Database

    • APEX

  4. Choose a deployment type.
    • Shared Infrastructure

      Run Autonomous Database on shared Exadata infrastructure.

    • Dedicated Infrastructure

      Run Autonomous Database on dedicated Exadata infrastructure.

    Select Shared Infrastructure to create your instance on shared Exadata infrastructure.

  5. Configure the database.
    • Always Free: Select to show Always Free configuration options.

      Always Free does not show when you select JSON workload type.

    • Choose database version Select the database version. The available database version is 19c.

      With Always Free selected, the available database versions are: 19c and 21c.

    • OCPU count Specify the number of CPU cores for your database.

      Your license type determines the OCPU count maximum. For example, if your license type is Bring Your Own License (BYOL) with Oracle Database Standard Edition (SE), the OCPU count maximum is 8.

    • OCPU auto scaling By default OCPU auto scaling is enabled to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand. If you do not want to use OCPU auto scaling then deselect this option.

      See Use Auto Scaling for more information.

    • Storage (TB) Specify the storage you wish to make available to your database, in terabytes.

    • Storage auto scaling By default storage auto scaling is disabled. Select if you want to enable storage auto scaling to allow the system to automatically expand to use up to three times more storage.

      See Use Auto Scaling for more information.

  6. Create administrator credentials. Set the password for the Autonomous Database Admin user.
    • Username This is a read only field.

    • Password Set the password for the Autonomous Database Admin user.

    • Confirm password Enter the same password again to confirm your new password.

    The password must meet the strong password complexity criteria based on Oracle Cloud security standards. For more information on the password complexity rules, see About User Passwords on Autonomous Database.

  7. Choose network access


    After you provision your Autonomous Database you can change the network access option you select for the instance.
    • Secure access from everywhere

      By default, secure connections are allowed from everywhere.

    • Secure access from allowed IPs and VCNs only

      This option restricts connections to the database according to the access control lists (ACLs) you specify. To add multiple ACLs for the Autonomous Database, click + Access Control Rule.

      See Configure Access Control Lists When You Provision or Clone an Instance for more information.

    • Private endpoint access only

      This option assigns a private endpoint, private IP, and hostname to your database. Specifying this option allows traffic only from the VCN you specify; access to the database from all public IPs or VCNs is blocked. This allows you to define security rules, ingress/egress, at the Network Security Group (NSG) level and to control traffic to your Autonomous Database.

      See Configure Private Endpoints When You Provision or Clone an Instance for more information.

  8. Choose license and Oracle Database Edition
    • Bring Your Own License (BYOL)

      Select if your organization already owns Oracle Database software licenses. Bring your existing database software licenses to the database cloud service. See Cloud pricing for information on Bring Your Own License (BYOL) and other licensing options for Oracle Cloud Infrastructure cloud service pricing.

    • Choose Oracle Database Edition

      When you select Bring Your Own License (BYOL), you also choose an Oracle Database Edition. The Oracle Database Edition you select is based on the license you bring to Autonomous Database and changes the maximum value that you can select for the OCPU count. The choices are:

      Oracle Database Enterprise Edition (EE): For this license type the maximum allowed value for OCPU count is 128. With auto scaling enabled you can use up to OCPU count x 3 OCPUs. For example, if you set the OCPU count to 128, you can use up to 384 OCPUs.

      Oracle Database Standard Edition (SE): For this license type the maximum allowed value for OCPU count is 8. With auto scaling enabled you can use up to OCPU count x 3 OCPUs. This license restricts the number of OCPUs you can use to a maximum of 8 OCPUs, with or without auto scaling enabled.

      See Use Auto Scaling for more information.

    • License Included

      Subscribe to new database software licenses and the database cloud service.

  9. (Optional) Provide up to 10 maintenance contacts

    Click Add Contact and in the Contact Email field, enter a valid email address. To enter multiple Contact Email addresses, repeat the process to add up to 10 customer contact emails.

    See View and Manage Customer Contacts for Operational Issues and Announcements for more information.

  10. (Optional) Click Show Advanced Options to select advanced options.
    • Encryption Key

      Encryption using Oracle-managed keys: By default Autonomous Database uses Oracle-managed encryption keys. Using Oracle-managed keys, Autonomous Database creates and manages the encryption keys that protect your data and Oracle handles rotation of the TDE master key.

      Encrypt using customer-managed keys: If you select customer-managed keys, a master encryption key in the Oracle Cloud Infrastructure Vault is used to generate the TDE master key on Autonomous Database.

      See Use Customer-Managed Encryption Keys on Autonomous Database for more information.

    • Maintenance

      Patch level By default the patch level is Regular. Select Early to configure the instance with the early patch level. Note: you cannot change the patch level after you provision an instance.

      See Set the Patch Level for more information.

    • Management

      Choose a character set and a national character set for your database.

      See Choose a Character Set for Autonomous Database for more information.

    • Tags

      If you want to use Tags, enter the TAG KEY and VALUE. Tagging is a metadata system that allows you to organize and track resources within your tenancy. Tags are composed of keys and values which can be attached to resources.

      See Tagging Overview for more information.

  11. Click Create Autonomous Database.

On the Oracle Cloud Infrastructure console the Lifecycle State shows Provisioning until the new database is available.