13 Cloning a Database with Autonomous Data Warehouse

Autonomous Data Warehouse provides cloning where you can choose to clone either the full database or only the database metadata.

Clone Autonomous Data Warehouse

Shows you the steps to clone an Autonomous Data Warehouse database using the Oracle Cloud Infrastructure Console.

  • Sign in to your Oracle Cloud Account at cloud.oracle.com.

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

  • From the Oracle Cloud Infrastructure left navigation list click Autonomous Data Warehouse.

  1. Choose your region. See Switching Regions for information on switching regions and working in multiple regions.
  2. Choose your Compartment. See Compartments for information on using and managing compartments.
  3. Select an Autonomous Data Warehouse instance from the list in your compartment.
  4. On the Details page, from the Actions drop-down list, select Create Clone.

    Create Clone is only enabled only when the instance state is Available or Available Needs Attention.

  5. In the Create Autonomous Database Clone page, enter the following information:
  6. Choose clone type from the choices:
    • Full Clone: creates a new database with the source database’s data and metadata.
    • Metadata Clone: creates a new database with the source database’s metadata without the data.
  7. Provide basic information for the Autonomous Database.
    • Create in Compartment. See Compartments for information on using and managing compartments.

    • Origin Database Name This is a read-only field that 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.

      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 14 characters.


      The same database name cannot be used for multiple Oracle Autonomous Database databases in the same tenancy in the same region.
  8. Configure the database.
    • CPU core count Specify the number of cores for your Autonomous Data Warehouse database.

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

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

    • Auto scaling Select to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand. See Use Auto Scaling for more information.

  9. Create administrator credentials.
    • Username This is a read-only field.

    • Password Set the password for the Autonomous Data Warehouse Admin user. 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 Users with Autonomous Data Warehouse.
    • Confirm password Specify a value to confirm the password.
  10. Choose a license type.
    • Bring Your Own License

      My organization already owns Oracle database software licenses. Bring my existing database software licenses to the database cloud service (details).

    • License Included

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

    (Optional) Click Show Advanced Options to enter additional options.

    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.

On the Oracle Cloud Infrastructure console the State shows Provisioning... until the new Autonomous Data Warehouse database is available.

For the clone operation, note the following:

  • Oracle Machine Learning workspaces, projects, and notebooks of the source database are not cloned to the new database.

  • If there is an ongoing clone operation on a source database, you cannot initiate a new clone operation on the database being cloned until the ongoing operation completes.

  • You can only clone an Autonomous Data Warehouse instance to the same tenancy and the same region as the source database.

See Cloning an Autonomous Database for information on using the API.

Optimizer Statistics for a Cloned Database

During the provisioning for either a Full Clone or a Metadata Clone, the optimizer statistics are copied from the source database to the cloned database.

The following applies for optimizer statistics for tables in a cloned database:

  • Full Clone: loads into tables behave the same as loading into a table with statistics already in place.
  • Metadata Clone: the first load into a table after the clone 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 and Performance Data for a Cloned Database

The following applies for resource management rules and performance data in a cloned database:

  • During the provisioning for either a Full Clone or a Metadata Clone, any resource management rule changed by the user in the source database is carried over to the cloned database.
  • Performance data for the time before the clone operation is not visible on the service console of the cloned database.

For more information on setting resource management rules, see Manage Runaway SQL Statements on Autonomous Data Warehouse.