Autonomous Transaction Processing provides cloning where you can choose to clone either the full database or only the database metadata.
Clone Autonomous Transaction Processing
Shows you the steps to clone an Autonomous Transaction Processing 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 next to Oracle Cloud.
From the Oracle Cloud Infrastructure left navigation list click Autonomous Transaction Processing.
- Choose your region. See Switching Regions for information on switching regions and working in multiple regions.
- Choose your Compartment. See Compartments for information on using and managing compartments.
- Select an Autonomous Transaction Processing instance from the list in your compartment.
- 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.
- In the Create Autonomous Database Clone dialog, enter the following:
- Clone Type
- 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.
Compartment: Select a compartment from the list of available compartments.
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.
CPU Core Count: Specify the number of cores for your Autonomous Transaction Processing database.
Storage (TB): Specify the storage you wish to make available to your Autonomous Transaction Processing 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.
Administrator Credentials: Set the password for the Autonomous Transaction Processing 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 Transaction Processing.
License Type: The type of license you want to use for the Autonomous Database.
My organization already owns Oracle database software licenses. Bring my existing database software licenses to the database cloud service (details).
Subscribe to new database software licenses and the database cloud service.
- Clone Type
- Click Create Autonomous Database Clone.
Your display shows Provisioning until the new Autonomous Database 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 Transaction Processing 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 Transaction Processing.