Clone Type and Source

The only supported clone type for ACDs is Full Clone, which includes the metadata and data from the source container database and Autonomous Databases within it.

The clone source for an ACD clone can only be a Clone from backup from the latest available timestamp.

While cloning an ACD, you may:

• Choose a different Exadata Infrastructure or Autonomous Exadata VM Cluster for the clone database.
• Create the clone ACD in the same region or a region different from the clone source.

After submitting a clone request, the clone database shows up as PROVISIONING until the new ACD is available. You cannot initiate a new clone operation on an ACD that is already being cloned until the ongoing operation completes.

Clone Requirements

When cloning an ACD:

• You must have a different Autonomous Database Exadata VM Cluster (AVMC) available for the destination of the clone.
• The destination AVMC requires 0.5 OCPUs or 2 ECPUs available for each ADB in the ACD being cloned.
• The target AVMC should have the same major database version as the destination AVMC.
• Your keystore should be accessible and allow-listed from the target AVMC.

Clone Limitations

Note the following limitations with cloning an ACD:

• You cannot clone an ACD to an AVMC if there are any Autonomous Databases inside the source ACD that already exist in the AVMC. There cannot be duplicate Autonomous Databases.
• Access control lists and auto scaling are disabled in the ACD clone.
• You can only clone an ACD from an existing timestamp, not previous backups.
• The cloned Autonomous Databases will each have the minimum allowed ECPUs/OCPUs allocated to them.

Step-by-Step Guides

To learn how to clone an ACD using the OCI console, see Clone an Autonomous Container Database.

You can also use the CreateAutonomousContainerDatabase API to clone a database. For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.