About Cloning Autonomous Container Database on Dedicated Exadata Infrastructure
Cloning an Autonomous Container Database (ACD) creates a point-in-time copy of your ACD and the Autonomous AI Databases within it. You can use the cloning feature to quickly set up an ACD from the latest available timestamp for purposes such as testing, development, or analytics.
Clone Type and Source
You can create the following clone types of an ACD:
-
Full Clone: Create a new ACD that includes the metadata and data from the source container database and Autonomous AI Databases within it.
-
Partial Clone: Create a new ACD that includes a subset of Autonomous AI Databases from a source container database.
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. Only one clone operation at a time is allowed, meaning that you cannot initiate multiple ACD clone operations on the same target Autonomous Exadata VM Cluster (AVMC).
Clone Requirements
When cloning an ACD:
-
You must have a different Autonomous 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 database version as the source AVMC.
-
Your keystore should be accessible and allow-listed from the target AVMC.
- For a cross-region ACD clone, create a key store in the target region and provide the Oracle Key Vault (OKV) connection details, including the IP addresses and the administrator credentials (username and password).
Clone Limitations
Note the following limitations with cloning an ACD:
-
You cannot clone an ACD to an AVMC if there are any Autonomous AI Databases inside the source ACD that already exist in the AVMC. There cannot be duplicate Autonomous AI Databases. The target AVMC must not contain an Autonomous AI Database with the same database name as any Autonomous AI Database in the source ACD.
-
Access control lists and auto scaling are disabled in the ACD clone.
-
The cloned Autonomous AI Databases will each have the minimum allowed ECPUs/OCPUs allocated to them.
-
You cannot create a partial clone or clone from a timestamp when cloning an ACD from a remote backup.
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.