Shows you the steps to create an Autonomous Database refreshable clone from the Oracle Cloud Infrastructure Console.
Perform the following prerequisite steps as necessary:
Open the Oracle Cloud Infrastructure console by clicking the next to Oracle Cloud.
- From the Oracle Cloud Infrastructure left navigation list click either Autonomous Data Warehouse, Autonomous Transaction Processing, or Autonomous JSON Database depending on the workload type of your Autonomous Database.
On the Autonomous Databases page select your Autonomous Database from the links under the Display Name column.
To create a refreshable clone do the following:
- On the Details page, from the More Actions drop-down list, select Create Clone.
- On the Create
Clone page, choose the clone type Refreshable
Clone from the choices:
- Full Clone: creates a new database with the source database’s data and metadata.
- Refreshable Clone To create a refreshable clone, select this clone type.
- Metadata Clone: creates a new database with the source database’s metadata without the data.
- Provide basic information for the Autonomous Database clone.
Create in Compartment. See Compartments for information on using and managing compartments.
Source database name This field is read-only and shows the name of the source database.
Display Name Specify a user-friendly description or other information that helps you easily identify the database.
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.
Note:After you create a refreshable clone you cannot change the display name. If you specify the default name, Clone of DBname, when you create a refreshable clone and you later disconnect the clone from the source database to use the database as a standard read/write database, the database keeps the name you specify when you create the refreshable clone. Thus, using the Clone of prefix may not be the display name you want to specify when you create a refreshable clone.
Database Name: Specify the database name; it must consist of letters and numbers only. The maximum length is 14 characters. The same database name cannot be used for multiple Autonomous Databases in the same tenancy in the same region.
- Configure the database.
OCPU Count Specify the number of CPU cores for your database.
Auto scaling Auto scaling is enabled by default. You can deselect this option to disable auto scaling. With auto scaling the system to automatically uses up to three times more CPU and IO resources to meet workload demand.
Note:The storage for a refreshable clone is set to the same size as on the source database. To change the storage size for a refreshable clone, you must change the storage value on the source database.
- Choose network access.
Allow secure access from everywhere
By default all secure connections are allowed from everywhere. To restrict access configure an access control list (ACL). To add an ACL for the Autonomous Database, select Configure access control rules.
Virtual cloud network
This option assigns a private endpoint, private IP, and hostname to your database. Specifying this option allows traffic only from the VCN you specify; access to the database from all public IPs or VCNs is blocked. This allows you to define security rules, ingress/egress, at the Network Security Group (NSG) level and to control traffic to your Autonomous Database.
- Choose a license type.
- Click Create Autonomous Database Clone.
On the Oracle Cloud Infrastructure console the State shows Provisioning... until the refreshable clone is available.
After the provisioning completes the Lifecyle State shows Available and the Mode is Read-only.
After you download the wallet for the refreshable clone and connect to the database, you can begin using the database to perform read-only operations such as running queries or building reports and notebooks.
After you create a refreshable clone, the Oracle Cloud Infrastructure console shows a banner similar to the following with a message indicating the date prior to which the next refresh must be completed (the banner shows the 7 day refresh limit).
Description of the illustration adb_refreshable_clone_refresh_clone.png
See Refresh a Refreshable Clone on Autonomous Database for details on refreshing a refreshable clone.