I will describe how to clone an existing Autonomous Database using the Oracle Cloud Infrastructure Console. You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing or development.
There are 2wo types of Autonomous Database clones:
The full-clone option: It creates a database that includes the metadata and data from the source database.
The metadata-clone option: It creates a database that includes only the metadata from the source database.
You can use a running database to create a clone. For databases running on shared Exadata infrastructure, you can also use a backup as the source of your clone. When using a backup, you can select a listed backup to clone from, or create a point-in-time clone. Point-in-time clones contain all data up to a specified timestamp. The specified timestamp must be in the past.
Let me do a clone of an Autonomous Database to shared Exadata infrastructure
1- Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
2- If you are not already in the correct compartment, then choose one from the Compartment drop-down in the List Scope section that contains the database you want to clone.
3- In the list of Autonomous Databases, click the display name of the database you want to clone.
4- Go to Actions, and then click Create Clone.
5- In the Create Autonomous Database Clone dialog, select the following:
Clone Type: Select the type of clone you want to create. Choose either Full Clone or Metadata Clone.
Clone Source: The clone source selection allows you to specify whether the clone is created from a running database or from a database backup. Select one of the following options:
Clone from running database: Creates a clone of a running database as it exists at the current moment.
Clone from a backup: Creates a clone from a database backup. If you choose this option, select one of the following options:
Specify a timestamp: Creates a point-in-time clone.
Select from a list of backups: Creates a clone using all data from the specified backup. To limit your list of backups to a specific date range, enter the starting date in the From field and the ending date in the To field.
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.
Choose database version: Select a database version from the available versions.
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: 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.
Administrator Credential: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.
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.
6- Finally Click Create Autonomous Database Clone at the bottom of page.
7- The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database.
After a few minutes, our new clone autonomous database will be ready.