Create a Refreshable Clone for an Autonomous Database Instance

Shows you the steps to create an Autonomous Database refreshable clone from 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.
  • On the Autonomous Databases page select your Autonomous Database from the links under the Display Name column.

To create a refreshable clone do the following:

  1. On the Details page, from the More Actions drop-down list, select Create Clone.
  2. On the Create Autonomous Database Clone page, choose the clone type Refreshable Clone from the choices:
    • Full Clone: creates a new database with the source database’s data and metadata.
    • Refreshable Clone To create a refreshable clone, select this clone type.
    • Metadata Clone: creates a new database with the source database’s metadata without the data.
  3. Provide basic information for the Autonomous Database clone.
    • Create in Compartment. See Compartments for information on using and managing compartments.

    • Source database name This field is read-only and shows the name of the source database.

    • Display name Specify a user-friendly description or other information that helps you easily identify the database.

      You can use the name provided, of the form: Clone-of-DBname or change this to the name you want to use to identify the database. The supplied DBname is the name of the source database that you are cloning.

    • 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.

      The default database name is a generated 16-character string.

  4. Configure the database.
    • 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.


    The storage for a refreshable clone is set to the same size as on the source database. To change the storage size for a refreshable clone, you must change the storage value on the source database.
  5. Choose network access


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

      By default all 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.

  6. 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 an 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, however you may contact your Oracle account team to request more than 128 OCPUs. 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.

  7. (Optional) Provide up to 10 maintenance contacts.

    Click Add Contact and in the Contact Email field, enter a valid email address. If the database you are cloning has a customer contact list, the list is copied. 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.

  8. (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 the patch level of the source database. Select Early to configure the instance with the early patch level. When cloning a source database with Early patch level, you can only choose the Early patch level for your clone.

      See Set the Patch Level for more information.

    • Management

      Shows the character set and 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.

  9. Click Create Autonomous Database Clone.

On the Oracle Cloud Infrastructure console the State shows Provisioning... until the refreshable clone is available.

After the provisioning completes the Lifecycle State shows Available and the Mode is Read-only.

After you download the wallet for the refreshable clone and connect to the database, you can begin using the database to perform read-only operations such as running queries or building reports and notebooks.

After you create a refreshable clone, the Oracle Cloud Infrastructure console shows a banner similar to the following with a message indicating the date prior to which the next refresh must be completed (the banner shows the 7 day refresh limit).

Description of adb_refreshable_clone_refresh_clone.png follows
Description of the illustration adb_refreshable_clone_refresh_clone.png

See Refresh a Refreshable Clone on Autonomous Database for details on refreshing a refreshable clone.