This topic describes how to clone an existing Autonomous Database using the Oracle Cloud Infrastructure Console or the API. You may wish to use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development or analytics. If you need to clone only the database schema of your source database, the Console's cloning feature is a quick and easy way to accomplish this task.
This topic is not applicable to Autonomous Databases using the dedicated deployment option.
The clone feature offers the following two types of Autonomous Database clones:
- The full clone option creates a new database that includes all of the source database's metadata and data.
- The metadata clone option creates a new database that includes the source database's metadata, but not the source database's data.
- To clone an Autonomous Database, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in. See Authentication and Authorization for more information on user authorizations for the Oracle Cloud Infrastructure Database service.
To clone an Autonomous Database
Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
- Choose your Compartment.
- In the list of Autonomous Databases, click on the display name of the database you wish to clone.
Hover over the Actions button, and then click Create Clone.
In the Create Autonomous Database Clone dialog, enter the following:
Select the type of clone you wish to create. Choose either Full Clone or Metadata Clone.
- Compartment:Your current compartment is the default selection.
- Display Name: 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 like. Avoid entering confidential information.
- Database Name: The database name must consist of letters and numbers only, starting with a letter. The maximum length is 14 characters. Avoid entering confidential information.
CPU Core Count: You can enable up to 128 cores for your Autonomous Database. The actual number of available cores is subject to your tenancy's service limits.
Auto Scaling: Auto scaling allows Autonomous Databaseto automatically increase the number of CPU cores by up to three times the assigned CPU core count value, depending on demand for processing. The auto scaling feature reduces the number of CPU cores when additional cores are not needed. For databases with up to 42 assigned cores, you can increase the maximum number of cores available through auto scaling by increasing the CPU core count value.
The maximum number of cores that are available to any Autonomous Database database not using dedicated deployment is 128, regardless of whether auto scaling is enabled or not. This means that database with a CPU core count of 64 could auto scale up to two times the assigned number of cores (2 x 64 = 128). A database with 42 cores (or fewer) could auto scale up to three times the assigned number (3 x 42 = 126). For billing purposes, the database service determines the average number of CPUs used per hour.
Storage: Specify the storage you wish to make available to your Autonomous Database database, in terabytes. You can make up to 128 TB available. For full clones, the size of the source database determines the minimum amount of storage you can make available.
Set the password for the Autonomous Database Admin user by entering a password that meets the following criteria. You use this password when accessing the Autonomous Database service console and when using an SQL client tool.
- Between 12 and 30 characters long
- Contains at least one lowercase letter
- Contains at least one uppercase letter
- Contains at least one number
- Does not contain the double quotation mark (")
- Does not contain the string "admin", regardless of casing
The type of license you want to use for the Autonomous Transaction Processing database. Your choice affects metering for billing. You have the following options:
- My Organization Already Owns Oracle Database Software Licenses: This choice is used for the Bring Your Own License (BYOL) license type. If you choose this option, make sure you have proper entitlements to use for new service instances that you create.
- Subscribe to New Database Software Licenses and the Database Cloud Service: This is used for the License Included license type. With this choice, the cost of the cloud service includes a license for the Database service.
Click Create Autonomous Database Clone.
The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:
- The new clone displays the Provisioning lifecycle state until the provisioning process completes.
- The source database remains in the Available lifecycle state.
- Backups associated with the source database are not cloned for either the full clone or the metadata clone option.
- Oracle recommends that you evaluate the security requirements for the new database and implement them, as applicable. See Security Considerations for details.
Using the API
Use the CreateAutonomousDatabase API operation to clone an Autonomous 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.