Oracle Cloud Infrastructure Documentation

Cloning an Autonomous Database

This topic describes how to clone an existing Autonomous Database using the Oracle Cloud Infrastructure Console or the API. You can 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 want to clone only the database schema of your source database, then choose the metadata clone option.

Note

You can clone any existing Autonomous Database (including those provisioned with preview version software) using a preview version of Autonomous Database. However, preview-version databases cannot be cloned using the regular (general-availability) Autonomous Database software.

Clone Types

The clone feature offers the following two types of Autonomous Database clones:

  • The full-clone option creates a database that includes the metadata and data from the source database.
  • The metadata-clone option creates a database that includes only the metadata from the source database.

Clone Sources

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.

Note

When you create a clone from a backup, you must select a backup that is at least two hours old.

Prerequisites

To clone an Autonomous Database, you must be given the required type of access in a policy  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 compartment  you should work in. See Authentication and Authorization for more information on user authorizations for the Oracle Cloud Infrastructure Database service.

Password Requirement for New Databases on Dedicated Exadata Infrastructure

When cloning a database on dedicated Exadata infrastructure, the password you set for the target database cannot be one of the three most recently used passwords of the source database.

Using the Oracle Cloud Infrastructure Console

To clone an Autonomous Database to shared Exadata infrastructure
To clone an Autonomous Database to dedicated Exadata infrastructure

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.

For More Information

For information about optimizer statistics, resource management rules and performance data for a cloned database, see the Using Oracle Autonomous Data Warehouse and Using Oracle Autonomous Transaction Processing user guides.