Clone Autonomous AI Database to Change Workload Type

When you create an Autonomous AI Database clone, by default the clone is of the same workload type. Optionally, you can select that the clone is of a different workload type than the source database.

Cloning a database to a different workload type is useful when:

• You have provisioned a database of an incorrect workload type and now need to clone the database to the appropriate workload type.

• You need a copy of your database of a different workload type to branch out to run new types of workloads on your data.

Note the following when you clone to a different workload type:

• You can clone between the following workload types:

  • Autonomous AI Lakehouse to Autonomous AI Transaction Processing

  • Autonomous AI Transaction Processing to Autonomous AI Lakehouse

  • Autonomous AI JSON Database to Autonomous AI Transaction Processing or Autonomous AI Lakehouse or APEX Service

  • APEX Service to Autonomous AI JSON Database or Autonomous AI Transaction Processing or Autonomous AI Lakehouse

• You may also clone from a backup, when choosing to clone a database to a different workload type.

• The cloned database can be in the same region or in a different region (cross region).

• Cloning a database to a different workload type does not affect the database's existing data dictionary, optimizer statistics, and object compression. New objects that are created after cloning are created using the cloned database's workload type parameters (for example compression and statistics).

The following are not allowed when you clone and select a different workload type:

• Creating a cross workload refreshable clone.

• Cloning to a more restrictive workload type, such as from Autonomous AI Transaction Processing or Autonomous AI Lakehouse database to Autonomous AI JSON Database or APEX Service.

See the following for steps to create an Autonomous AI Database clone:

• Clone an Autonomous AI Database Instance

• Clone an Autonomous AI Database from a Backup