Clone an Autonomous Transaction Processing Dedicated Database


The speed of the clone operation depends on the number of OCPUs you specify for the clone you are creating. Therefore, you can improve the speed of the clone operation by specifying more OCPUs for clone and then scaling it down to the desired number of OCPUs (as described in Remove CPU or Storage Resources from an Autonomous Transaction Processing Dedicated Database) after the clone operation completes.

Follow these steps to use the Oracle Cloud Infrastructure console.

  1. Go to the Details page of the Autonomous Transaction Processing dedicated database you want to clone.


    For dedicated databases that use Autonomous Data Guard, go to the Details page of the primary database.

    For instructions, see View Details of an Autonomous Transaction Processing Dedicated Database.

  2. On the Details page, select More Actions and then select Create Clone.

    Create Clone is only enabled only when the database's state is Available or Available Needs Attention.

  3. On the Create Autonomous Database Clone page, enter the following information:
    • Choose Clone Type: choose Full Clone or Metadata Clone.
      • The full clone option creates a new database that includes all of the source database's metadata and data.
      • The metadata clone option creates a new database that includes the source database's metadata, but not the source database's data.
    • Provide basic information:
      • Create in Compartment. See Compartments for information on using and managing compartments.
      • Source Database Name. This read-only field identifies the name of the source database.
      • 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.
      • Database Name. Specify the database name; it must consist of letters and numbers only. The maximum length is 14 characters.


        The same database name cannot be used for multiple Autonomous Databases in the same tenancy in the same region.
      • Autonomous Container Database. Specify the Autonomous Container Database in which to place the cloned database. The default is the same Autonomous Container Database as the source database.
    • Configure the database:
      • OCPU count Specify the number of OCPUs for your dedicated database.
      • Storage (TB) Specify the storage you wish to make available to your dedicated database, in terabytes.

        For a Full Clone, the minimum storage that you can specify is the source database's actual used space rounded up to the next TB.

      • Auto Scaling: Enable or disable auto scaling, which permits Autonomous Transaction Processing to automatically use up to three times as many OCPUs as specified by OCPU Count as the workload on the database increases.

    • Create administrator credentials
      • Username This is a read-only field.
      • Password Set the password for the ADMIN database user in the cloned dedicated 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.


        You must specify a different password from the one for the ADMIN database user in the source database; otherwise, the clone operation will fail.
      • Confirm password Specify a value to confirm the password.
    • Access Control List

      Add or modify entries, as applicable. See Set Access Control List for an Autonomous Transaction Processing Dedicated Database for details.

      AvailabilityChoosing a network access type and setting an ACL is not currently supported for Autonomous Transaction Processing dedicated databases on Oracle Cloud.

    • Show Advanced Options (Optional)

      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.

  4. Click Create Autonomous Database Clone.

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

Note that you cannot initiate a new clone operation on a dedicated database that is already being cloned until the ongoing operation completes.

Also, note the following information about the newly cloned dedicated database:

  • Optimizer statistics are copied from the source database to the cloned database. Then:
    • For full clones, loads into tables behave the same as loading into a table with statistics already in place.
    • For metadata clones, the first load into a table clears the statistics for that table and updates the statistics with the new load.

    For more information on Optimizer Statistics, see Optimizer Statistics Concepts.

  • Resource management rules changed by the user in the source database are carried over to the cloned database.
  • Performance data for the time before the clone operation is not available in the cloned database.