Prerequisites

To view the requirements for successfully cloning an ACD instance, see About Cloning Autonomous Container Database on Dedicated Exadata Infrastructure.

Required IAM Policies

manage autonomous-container-databases

use cloud-exadata-infrastructures

use cloud-autonomous-vmclusters

Procedure

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

   For instructions, see View Details of an Autonomous Container Database.

2. Under More actions, click the Create Clone button.
3. Fill out the Clone Autonomous Container Database page with the following information:

   Setting	Description	Notes
   Compartment	Select a compartment to host the Autonomous Container Database.
   Display name	Enter a user-friendly description or other information that helps you easily identify the resource.	The display name does not have to be unique and you can change it whenever you want. Avoid entering confidential information.
   Container Database Name	Enter a name for the container database. It can contain only letters and numbers. Starting with a letter and a maximum of 30 characters.	The container database name must be unique across the Autonomous Exadata VM Cluster. Tip: The container database name is used to name the Oracle Key Vault's (OKV) wallet. You can use this name to locate the OKV wallet associated with your Autonomous Container Database on your OKV console.
   Exadata Infrastructure	The Exadata Infrastructure to host the new Autonomous Container Database.	To create a Mulitcloud ACD resource, set the resource compartment selector to your Multicloud compartment, then select the desired Exadata Infrastructure.
   Autonomous Exadata VM Cluster	The Autonomous Exadata VM Cluster to host the new Autonomous Container Database.	To create a Mulitcloud ACD resource, set the resource compartment selector to your Multicloud compartment, then select the desired Autonomous Exadata VM Cluster.
   Configure automatic maintenance	The panel to configure automatic maintenance displays the following default settings: Maintenance method: Rolling with time-zone file update disabled. Container database maintenance version: Next release update (RU) Maintenance schedule: No schedule preference specified. Optionally, you can configure a maintenance preference or schedule by clicking Modify maintenance schedule that launches the Edit automatic maintenance dialog.	DST stands for Daylight Savings Time.
   Edit automatic maintenance	Configure maintenance method: Choose between Rolling or Non-rolling maintenance methods. Optionally, you can also select Enable time-zone update. See Service Maintenance Types for more information. Configure container database maintenance version: Choose either Next RU or Latest RU to configure the next maintenance version of the ACD. Configure automatic maintenance schedule: Optionally, you can change the maintenance schedule from the default (No preference, which permits Oracle to schedule maintenance as needed) to Custom schedule in Oracle Public Cloud and Specify a schedule in Exadata Cloud@Customer. For guidance on choosing a custom schedule, see Settings in Maintenance Schedule that are Customizable. Click Save to close this dialog.	Updating the time-zone file would require a complete downtime for the ACD and the associated Autonomous Databases. The downtime is dependent on the amount of data that is time-zone sensitive. All the RUs that include a time-zone update will be patched in the non-rolling maintenance method (with full system downtime) only. So, if you configure your maintenance to the rolling method and enable time-zone update, all the RUs that include a time-zone update are applied in the non-rolling method only. Only those RUs without a time-zone update are applied in the rolling method. In an Autonomous Data Guard configuration, the non-rolling maintenance method results in downtime for the primary and standby ACDs during their respective maintenance window until the patching completes.
   Configure backups: Enable automatic backups	By default, automatic backups are enabled for an ACD. Optionally, you can choose to disable them by deselecting the Enable automatic backups check box. While provisioning an ACD with Autonomous Data Guard, you can not disable the automatic backups.	If disabled for an ACD, automatic backups can be enabled anytime later from the Oracle Cloud Infrastructure (OCI) console by following the steps outlined in Edit Autonomous Container Database Backup Settings. However, once enabled you can not disable automatic backups for the ACD. If enabling automatic backups fail for some reason, the ACD provisioning also fails with an error message. As a workaround, you can provision the ACD with automatic backups disabled, and enable them from the ACD's Details page later.
   Configure backups: Backup retention period (in days)	After enabling automatic backups, specify a Backup retention period value to meet your needs. You can choose any value between 7 to 95 days.	The backup retention policy value defaults to 15 days. All the backups are automatically deleted after the backup retention period.
   Configure backups: Enable cross-region backup copy	Optionally, select Enable cross-region backup copy and specify a region for the backup copies.	Cross region backup copy cannot be enabled on Autonomous Data Guard enabled ACDs. Cross-region backup copy cannot be enabled on Multicloud ACD resources.
   Show/hide advanced options	By default, advanced options are hidden. Click Show advanced options to display them.
   Advanced options: Management	Optionally, you can define a suitable value for the following resource management attributes to suit your needs: Database split threshold (CPU): The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 64 for ECPUs and 16 for OCPUs. Node failover reservation (%): Determines the percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option. Distribution affinity: Determines whether an Autonomous Database must be opened across a minimum or maximum of nodes. By default, Minimum nodes is selected with Maximum nodes being the other option. Optionally, select Enable shared server connections to support the Net services architecture.	If the Node failover reservation is set to 0%, your Autonomous Database may face a complete outage during VM failure and maintenance operations such as database patching and container database restart. The shared server architecture enables a database server to allow many client processes to share very few server processes, so the number of users that can be supported is increased. You cannot disable shared server architecture after provisioning the ACD. See Special-Purpose Connection Features for more details.
   Advanced options: Encryption Key	Optionally, you can configure the Autonomous Container Database to use customer-managed encryption keys instead of Oracle-managed encryption keys. Select Encrypt using a customer-managed key in this tenancy and one of the following options, depending on your deployment: OCI Vault Service: With this option, choose a Vault and a Master Encryption Key from the lists. This option is only available on Oracle Public Cloud. Oracle Key Vault: With this option, you must choose a key store that is same as that of the source ACD.	By default, Encrypt using Oracle-managed keys is selected. You need to create a key store to use encryption key with Oracle Key Vault. See Use Customer-Managed Keys in Oracle Key Vault for instructions.  You can use customer-managed encryption keys with Autonomous Data Guard-enabled Autonomous Container Databases with the primary and standby databases located in different availability domains within the same region. For information about using customer-managed keys see About Master Encryption Keys.
   Advanced options: Tags	If you want to use tags, add tags by selecting a Tag Namespace, Tag Key, and Tag Value.	You can not modify the time zone settings for an Autonomous Exadata VM Cluster already provisioned. If needed, you can create a service request in My Oracle Support. For help with filing a support request, see Create a Service Request in My Oracle Support.

4. Click Clone Autonomous Container Database.

Prerequisites

To view the requirements for successfully cloning an ACD instance, see About Cloning Autonomous Container Database on Dedicated Exadata Infrastructure.

Required IAM Policies

manage autonomous-container-databases

use cloud-exadata-infrastructures

use cloud-autonomous-vmclusters

Procedure

1. Go to the Remote backups page of your compartment.

   For instructions, see View a List of Remote Backups.

2. Click the three dots next to the remote backup that you want to clone, and then click Create Clone.
3. Fill out the Clone Autonomous Container Database page with the following information:

   Setting	Description	Notes
   Compartment	Select a compartment to host the Autonomous Container Database.
   Display name	Enter a user-friendly description or other information that helps you easily identify the resource.	The display name does not have to be unique and you can change it whenever you want. Avoid entering confidential information.
   Container Database Name	Enter a name for the container database. It can contain only letters and numbers. Starting with a letter and a maximum of 30 characters.	The container database name must be unique across the Autonomous Exadata VM Cluster. Tip: The container database name is used to name the Oracle Key Vault's (OKV) wallet. You can use this name to locate the OKV wallet associated with your Autonomous Container Database on your OKV console.
   Exadata Infrastructure	The Exadata Infrastructure to host the new Autonomous Container Database.	To create a Mulitcloud ACD resource, set the resource compartment selector to your Multicloud compartment, then select the desired Exadata Infrastructure.
   Autonomous Exadata VM Cluster	The Autonomous Exadata VM Cluster to host the new Autonomous Container Database.	To create a Mulitcloud ACD resource, set the resource compartment selector to your Multicloud compartment, then select the desired Autonomous Exadata VM Cluster.
   Configure automatic maintenance	The panel to configure automatic maintenance displays the following default settings: Maintenance method: Rolling with time-zone file update disabled. Container database maintenance version: Next release update (RU) Maintenance schedule: No schedule preference specified. Optionally, you can configure a maintenance preference or schedule by clicking Modify maintenance schedule that launches the Edit automatic maintenance dialog.	DST stands for Daylight Savings Time.
   Edit automatic maintenance	Configure maintenance method: Choose between Rolling or Non-rolling maintenance methods. Optionally, you can also select Enable time-zone update. See Service Maintenance Types for more information. Configure container database maintenance version: Choose either Next RU or Latest RU to configure the next maintenance version of the ACD. Configure automatic maintenance schedule: Optionally, you can change the maintenance schedule from the default (No preference, which permits Oracle to schedule maintenance as needed) to Custom schedule in Oracle Public Cloud and Specify a schedule in Exadata Cloud@Customer. For guidance on choosing a custom schedule, see Settings in Maintenance Schedule that are Customizable. Click Save to close this dialog.	Updating the time-zone file would require a complete downtime for the ACD and the associated Autonomous Databases. The downtime is dependent on the amount of data that is time-zone sensitive. All the RUs that include a time-zone update will be patched in the non-rolling maintenance method (with full system downtime) only. So, if you configure your maintenance to the rolling method and enable time-zone update, all the RUs that include a time-zone update are applied in the non-rolling method only. Only those RUs without a time-zone update are applied in the rolling method. In an Autonomous Data Guard configuration, the non-rolling maintenance method results in downtime for the primary and standby ACDs during their respective maintenance window until the patching completes.
   Configure backups: Enable automatic backups	By default, automatic backups are enabled for an ACD. Optionally, you can choose to disable them by deselecting the Enable automatic backups check box. While provisioning an ACD with Autonomous Data Guard, you can not disable the automatic backups.	If disabled for an ACD, automatic backups can be enabled anytime later from the Oracle Cloud Infrastructure (OCI) console by following the steps outlined in Edit Autonomous Container Database Backup Settings. However, once enabled you can not disable automatic backups for the ACD. If enabling automatic backups fail for some reason, the ACD provisioning also fails with an error message. As a workaround, you can provision the ACD with automatic backups disabled, and enable them from the ACD's Details page later.
   Configure backups: Backup retention period (in days)	After enabling automatic backups, specify a Backup retention period value to meet your needs. You can choose any value between 7 to 95 days.	The backup retention policy value defaults to 15 days. All the backups are automatically deleted after the backup retention period.
   Configure backups: Enable cross-region backup copy	Optionally, select Enable cross-region backup copy and specify a region for the backup copies.	Cross region backup copy cannot be enabled on Autonomous Data Guard enabled ACDs. Cross-region backup copy cannot be enabled on Multicloud ACD resources.
   Show/hide advanced options	By default, advanced options are hidden. Click Show advanced options to display them.
   Advanced options: Management	Optionally, you can define a suitable value for the following resource management attributes to suit your needs: Database split threshold (CPU): The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 64 for ECPUs and 16 for OCPUs. Node failover reservation (%): Determines the percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option. Distribution affinity: Determines whether an Autonomous Database must be opened across a minimum or maximum of nodes. By default, Minimum nodes is selected with Maximum nodes being the other option. Optionally, select Enable shared server connections to support the Net services architecture.	If the Node failover reservation is set to 0%, your Autonomous Database may face a complete outage during VM failure and maintenance operations such as database patching and container database restart. The shared server architecture enables a database server to allow many client processes to share very few server processes, so the number of users that can be supported is increased. You cannot disable shared server architecture after provisioning the ACD. See Special-Purpose Connection Features for more details.
   Advanced options: Encryption Key	Optionally, you can configure the Autonomous Container Database to use customer-managed encryption keys instead of Oracle-managed encryption keys. Select Encrypt using a customer-managed key in this tenancy and one of the following options, depending on your deployment: OCI Vault Service: With this option, choose a Vault and a Master Encryption Key from the lists. This option is only available on Oracle Public Cloud. Oracle Key Vault: With this option, you must choose a key store that is same as that of the source ACD.	By default, Encrypt using Oracle-managed keys is selected. You need to create a key store to use encryption key with Oracle Key Vault. See Use Customer-Managed Keys in Oracle Key Vault for instructions.  You can use customer-managed encryption keys with Autonomous Data Guard-enabled Autonomous Container Databases with the primary and standby databases located in different availability domains within the same region. For information about using customer-managed keys see About Master Encryption Keys.
   Advanced options: Tags	If you want to use tags, add tags by selecting a Tag Namespace, Tag Key, and Tag Value.	You can not modify the time zone settings for an Autonomous Exadata VM Cluster already provisioned. If needed, you can create a service request in My Oracle Support. For help with filing a support request, see Create a Service Request in My Oracle Support.

4. Click Clone Autonomous Container Database.