17 Cloning, Moving, or Upgrading an Autonomous Database

Autonomous Database provides cloning where you can choose to create a full clone, create a metadata clone, or create a refreshable clone. You can also use cloning to upgrade your database to a newer Oracle Database version when newer Oracle Database versions are available. You can move an Autonomous Database to a different Oracle Cloud Infrastructure compartment.

When you create a clone for an Autonomous Database instance, you have the option to select the clone type:

  • Full Clone: creates a new database with the source database's data and metadata.

  • Refreshable Clone: creates a read-only full clone that can be easily refreshed with the data from the source database.

    See Using Refreshable Clones with Autonomous Database for more information.

  • Metadata Clone: creates a new database that includes all of the source database schema metadata, but not the source database data.

For a Full Clone or a Metadata Clone, you have the option to select the clone source:

  • Clone from a database instance. This creates a clone of a running database.

  • Clone from a backup. This creates a clone when you select a backup from a list of backups, or when you enter a backup point-in-time to clone.

When you perform the clone operation you can select a newer Oracle Database version for the target database. This allows you to use cloning to upgrade Autonomous Database.

If your Autonomous Database instance is using Oracle Database 18c you can manually upgrade to Oracle Database 19c.

When an upcoming release is available for preview with Autonomous Database, you can clone your existing database or clone a backup, to use the preview version. A preview version is only available when there is an upcoming major version to release. At times no preview version will be available.