1. Go to the Details page of the Autonomous Database you want to clone.
   Note
   
   For databases that use Autonomous Data Guard, go to the Details page of the primary database.

   For instructions, see View Details of a Dedicated Autonomous 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.

3. Fill out the Create Autonomous Database Clone page with the following information:

   Setting	Description	Notes
   Clone type	Choose Full Clone or Metadata Clone.	See Clone Types for more details.
   Clone source	Select Clone from database instance.
   Autonomous Database clone: Compartment	Choose a compartment for the database clone.	See Understanding Compartments for information on using and managing compartments.
   Autonomous Database clone: Source database name	This read-only field identifies the name of the source database.
   Autonomous Database clone: 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.
   Autonomous Database clone: Database name	Specify a name for the clone database.	Database name 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.
   Region	Choose your preferred region to place the clone database.	The default is the same region as the source database.
   Exadata Infrastructure	Specify the Exadata Infrastructure to place the clone database.	The default is the same Exadata Infrastructure as that of the source database. You can choose an Exadata Infrastructure from a different compartment by clicking Change Compartment, if necessary.
   Autonomous Exadata VM Cluster	Specify the Autonomous Exadata VM Cluster (AVMC) to place the clone database.	The default is the same AVMC resource as that of the source database. You can choose an AVMC resource from a different compartment by clicking Change Compartment, if necessary.
   Autonomous Container Database	Specify the Autonomous Container Database (ACD) in which to place the cloned database. Start by choosing whether you want a standard ACD or an ACD configured to use Autonomous Data Guard. Click Change Compartment to select from a different compartment.	The default is the same ACD as that of the source database.
   Configure the database: Free instance	Toggle the Free instance button on if you want to create an Autonomous Database for Developers instance. The ECPU count and Storage (GB) are auto-populated with 4 and 32, respectively, because Autonomous Database for Developers instances come fixed at 4 ECPUs and 32GB of storage. Compute auto-scaling is disabled because developer database instances do not support manual or auto-scaling.	Autonomous Database for Developers is a free tier offering designed for database development and functional testing activities. For more details, see Autonomous Database for Developers. Developer database instances can only be created on ECPU-based ACDs without Autonomous Data Guard. Therefore, the Free instance toggle button is disabled for ACDs with OCPU, Autonomous Data Guard, or both. To successfully clone an Autonomous Database to an Autonomous Database for Developers, the actual used space of the source database, rounded up to the next GB, must be 32GB or less.
   Configure the database: CPU count:	Select the number of CPUs for your clone database from the list of provisionable CPUs.	The CPU type of the clone database (OCPU or ECPU) is determined by the clone's parent Autonomous Exadata VM Cluster compute type. You can clone an OCPU database into either OCPU or ECPU database. However, you can not clone an ECPU database into an OCPU database. This value defaults to 2 ECPUs or 1 OCPU depending on the CPU type. Refer to Compute Models in Autonomous Database for more details. You can also assign an 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.
   Configure the database: Auto scaling	Enable or disable auto scaling, which permits Autonomous Database to automatically use up to three times the allocated CPUs as the workload on the database increases.
   Configure the database: Storage (GB)	Specify the storage you wish to make available to your database in gigabytes (GB), with a minimum value same as the source database's current storage allocation.	For a Full Clone, the minimum storage that you can specify is the source database's actual used space rounded up to the next GB.
   Administrator credentials	Username: This is a read-only field auto-populated as ADMIN. Password: Set the password for the ADMIN database user in the cloned database. Confirm password: Re-enter the password for confirmation.	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.
   Configure network access	To enable database-level access control, click Modify Access Control and add or modify entries, as applicable.	See Set Access Control List for a Dedicated Autonomous Database for details.
   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 apply from the target Autonomous Container Database.	The source and target Autonomous Container Database's encryption key settings have to match for the clone to be successful.
   Advanced options: Management	The clone database inherits its Character Set and National Character Set values from its source.
   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.

4. Click Create Autonomous Database Clone.

1. Go to the Details page of the Autonomous Database you want to clone.

   For instructions, see View Details of a Dedicated Autonomous Database.

2. There are two ways to open the Create Autonomous Database Clone page from the Details page:

   • Option 1: Select More Actions and then select Create Clone.

     When you open the Create Autonomous Database Clone page using this option, you see additional options on this page that allows you to select a specific backup for cloning.

     Note
     
     Create Clone is enabled only when the database's state is Available.

   • Option 2: Scroll down to the bottom of the Details page, and click Backups under Resources. Then, click , and click Create Clone for the backup to be cloned.

     When you open the Create Autonomous Database Clone page using this option, the page launches with preselected backup for cloning. You do not see an option to choose a backup on this page again.

3. Fill out the Create Autonomous Database Clone page with the following information:

   Setting	Description	Notes
   Clone type	Choose Full Clone.	Metadata Clone is not supported when cloning from an Autonomous Database backup. See Clone Types for more details.
   Clone source	Select Clone from a backup.	When you open the Create Autonomous Database Clone page from the menu of a specific backup, this page launches with preselected backup for cloning. You do not see an option to choose a backup on this page again.
   Choose a specific backup	Once you select Clone from a backup, you see two additional options to choose a specific backup. Point in time clone: Select this option if you want to clone a backup with a specific timestamp. Selecting this option requires you to enter the backup timestamp in Enter Timestamp. You must enter a timestamp value within the last 60 days. Select the backup from a list: Select this option if you want to choose a backup from a list of backups. You can limit the number of backups you see by specifying a period using the From and To calendar fields.	Point in time clone is the default option. You can not use this option to clone a long-term backup. You must choose Select the backup from a list option if you want to clone from a long-term backup. You can only select one backup from the list that displays based on your input date range.
   Compartment	Choose a compartment for the database clone.	See Understanding 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 a name for the clone database.	Database name 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.
   Region	Choose your preferred region to place the clone database.	The default is the same region as the source database.
   Exadata Infrastructure	Specify the Exadata Infrastructure to place the clone database.	The default is the same Exadata Infrastructure as that of the source database. You can choose an Exadata Infrastructure from a different compartment by clicking Change Compartment, if necessary.
   Autonomous Exadata VM Cluster	Specify the Autonomous Exadata VM Cluster (AVMC) to place the clone database.	The default is the same AVMC resource as that of the source database. You can choose an AVMC resource from a different compartment by clicking Change Compartment, if necessary.
   Autonomous Container Database	Specify the Autonomous Container Database (ACD) in which to place the cloned database. Start by choosing whether you want a standard ACD or an ACD configured to use Autonomous Data Guard. Click Change Compartment to select from a different compartment.	The default is the same Autonomous Container Database as that of the source database.
   Configure the database: Free instance	Toggle the Free instance button on if you want to create an Autonomous Database for Developers instance. The ECPU count and Storage (GB) are auto-populated with 4 and 32, respectively, because Autonomous Database for Developers instances come fixed at 4 ECPUs and 32GB of storage. Compute auto-scaling is disabled because developer database instances do not support manual or auto-scaling.	Autonomous Database for Developers is a free tier offering designed for database development and functional testing activities. For more details, see Autonomous Database for Developers. Developer database instances can only be created on ECPU-based ACDs without Autonomous Data Guard. Therefore, the Free instance toggle button is disabled for ACDs with OCPU, Autonomous Data Guard, or both. To successfully clone a backup to an Autonomous Database for Developers, the source database's allocated space must be 32GB or less. If this condition is not met, you can attempt to clone the database instance to a developer database instead, provided that its actual used space, rounded up to the next GB, is 32GB or less.
   Configure the database: CPU count	Select the number of CPUs for your clone database from the list of provisionable CPUs. After the clone, you can resize to a lower value if needed. In case of OCPUs, you can even resize the CPU count to less than 1 OCPU (0.1 to 0.9 in increments of 0.1 OCPUs).	There is a minimum requirement of 2 OCPUs or 8 ECPUs for an Autonomous Database clone from Backup. The CPU type of the clone database (OCPU or ECPU) is determined by the clone's parent Autonomous Exadata VM Cluster compute type. Refer to Compute Models in Autonomous Database for more details. You can clone an OCPU database into either OCPU or ECPU database. However, you can not clone an ECPU database into an OCPU database. The total number of CPUs available to all databases within the Autonomous Exadata VM Cluster depends on the infrastructure shape and what is already allocated to other Autonomous Databases. The time taken to clone an Autonomous Database depends on the CPU Count and the network bandwidth between the Backup Destination and the target Autonomous Container Database. You can also assign an 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.
   Configure the database: Storage (GB)	Specify the storage you wish to make available to your database in gigabytes (GB), and it depends on the storage available to use.	The minimum storage that you can specify is the source database's current storage allocation.
   Configure the database: Auto scaling	Enable or disable auto scaling, which permits Autonomous Database to automatically use up to three times the allocated CPUs as the workload on the database increases.
   Administrator credentials	Username: This is a read-only field auto-populated as ADMIN. Password: Set the password for the ADMIN database user in the cloned database. Confirm password: Re-enter the password for confirmation.	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.
   Configure network access	To enable database-level access control, click Modify Access Control and add or modify entries, as applicable.	See Set Access Control List for a Dedicated Autonomous Database for details.
   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 apply from the target Autonomous Container Database.	The source and target can be different keystore types for encryption key. However, if both use customer managed keys using Oracle Key Vault (OKV), they must use the same OKV destination.
   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.

4. Click Create Autonomous Database Clone.

The steps demonstrated in this topic apply to cross tenancy cloning with the source database and the cloned database in the same region or different regions (cross-region).

To create a cross tenancy clone from an Autonomous Database instance, you must first ensure all the clone requirements are met. Specifically, you need to define the OCI Identity and Access Management policies to authorize cross tenancy cloning. See Cross Tenancy Clone Requirements for details.

On the tenancy where you want to create the clone, that is, on the destination tenancy in the destination region, use the CLI or call the REST API, specifying a valid clone type (Full or Metadata) and the OCID of the source database, which resides in a different tenancy (the source tenancy).

oci db autonomous-database create-from-clone 
    --clone-type metadata
    --compartment-id ocid1.compartment.oc1..unique_ID
    --source-id ocid1.autonomousdatabase.oc1..unique_ID
    --db-name dbnameclone 
    --display-name dbnameclone
    --admin-password <password>
    --data-storage-size-in-tbs 1 
    --compute-model ECPU
    --compute-count 4
    --autonomous-container-database-id ocid1.autonomouscontainerdatabase.oc1..unique_ID

oci raw-request 
    --debug 
    --http-method POST 
    --target-uri https://database.us-ashburn-1.oraclecloud.com/20160918/autonomousDatabases 
    --request-body '{
        "cloneType": "full",
        "displayName": "RAcloneV2",
        "dbName": "RAcloneV2",
        "compartmentId": "ocid1.compartment.oc1..unique_ID",
        "sourceId": "ocid1.autonomousdatabase.oc1..unique_ID",
        "autonomousContainerDatabaseId": "ocid1.autonomouscontainerdatabase.oc1..unique_ID",
        "adminPassword": "<password>",
        "dataStorageSizeInTBs": 1,
        "computeCount": 1,
        "computeModel": "ECPU",
        "isDedicated": "True"
    }'

This topic demonstrates the steps to create a cross tenancy clone from a backup.

To create a cross tenancy clone from an Autonomous Database backup, you must first ensure all the clone requirements are met. Specifically, you need to define the OCI Identity and Access Management policies to authorize cross tenancy cloning. See Cross Tenancy Clone Requirements for details.

On the tenancy where you want to create the clone, that is, on the destination tenancy in the destination region, use the CLI or call the REST API, specifying a valid clone type (Full or Metadata) and the OCID of the source database, which resides in a different tenancy (the source tenancy).

oci db autonomous-database create-from-backup-timestamp 
    --compartment-id ocid1.compartment.oc1..unique_ID
    --autonomous-database-id ocid1.autonomousdatabase.oc1..unique_ID
    --clone-type FULL 
    --timestamp 2024-04-16T20:30:00.123456Z
    --db-name ZZC08X42GU0B09GECA
    --display-name clonedb
    --admin-password <password>
    --data-storage-size-in-tbs 1 
    --compute-model ECPU
    --compute-count 4
    --autonomous-container-database-id ocid1.autonomouscontainerdatabase.oc1..unique_ID

oci raw-request
    --debug
    --http-method POST 
    --target-uri https://database.us-ashburn-1.oraclecloud.com/20160918/autonomousDatabases    
    --request-body '{
        "compartmentId": "ocid1.compartment.oc1..unique_ID",
        "dbName": "CTRAclonefrombackupid",
        "autonomousDatabaseBackupId": "ocid1.autonomousdatabasebackup.oc1..unique_ID",
        "cloneType": "FULL",
        "cpuCoreCount": 1,
        "dataStorageSizeInTBs": 1,
        "adminPassword": "<password>",
        "displayName": "CTRAclonefrombackupid",
        "autonomousContainerDatabaseId": "ocid1.autonomouscontainerdatabase.oc1..unique_ID",
        "source": "<BACKUP_FROM_ID>"
    }'

oci raw-request
    --debug 
    --http-method POST
    --target-uri https://database.us-ashburn-1.oraclecloud.com/20160918/autonomousDatabases 
    --request-body '{
        "compartmentId": "ocid1.compartment.oc1..unique_ID",
        "dbName": "CTbackuptimestamopRA",
        "autonomousDatabaseId":"ocid1.autonomousdatabase.oc1..unique_ID",
        "timestamp": "2024-07-17T02:20:15.123456Z",
        "cloneType": "FULL",
        "cpuCoreCount": 1,
        "dataStorageSizeInTBs": 1,
        "adminPassword": "<password>",
        "displayName": "CTbackuptimestamopRA",
        "autonomousContainerDatabaseId": "ocid1.autonomouscontainerdatabase..unique_ID",
        "source": "<BACKUP_FROM_TIMESTAMP>"
    }'