Provides general information about the cloning operation and the resulting cloned database.

• If the source database version is Oracle Database 19c, in regions where Oracle Database 23ai is available, you can choose either Oracle Database 19c or Oracle Database 23ai for the clone.

• If the source database version is Oracle Database 23ai, you can select Oracle Database 23ai for the clone.

• If there is an ongoing scaling operation on a source database, you cannot initiate a clone operation until the ongoing operation completes. If you attempt such an operation you will see message such as the following:

  The operation cannot be performed because the Autonomous Database with Id **** is in the SCALE_IN_PROGRESS state.

• If you define a network Access Control List (ACL) on the source database, the currently set network ACL is cloned to the new database. If a database is cloned from a backup, the current source database's ACL is applied (not the ACL that was valid at the time of the backup).

• If you create a clone and the source database has an access control list (ACL) and you specify the private endpoint network access option, Virtual cloud network for the target database, the ACL is not cloned to the new database. In this case, you must define security rules within your Network Security Group (or groups) to control traffic to and from your target database (instead of using the access control rules that were specified in the ACL on the clone source). See Configure Private Endpoints When You Provision or Clone an Instance for more information.

• Cloning an Autonomous Database instance copies your database files to a new instance. There is no downtime associated with cloning and the cloning operation has no impact on applications running on the source.

• For a Metadata Clone, the APEX Apps and the OML Projects and Notebooks are copied to the clone. For a Metadata Clone, the underlying database data of the APEX App or OML Notebook is not cloned.

• The Autonomous Database Details page for an Autonomous Database instance that was created by cloning includes the Cloned From field. This displays the name of the database where the clone was created.

• The value of the DBA_SERVICES.FAILOVER_TYPE column is not copied to a cloned Autonomous Database instance.

Provides information about cross tenancy and cross-region cloning.

• For cloning, when you choose a region other than the current region for your clone target, using either the Oracle Cloud Infrastructure CLI or Terraform you can only perform such a cross-region clone from the remote region. That is, call the create clone API from the remote region to which you want to clone, with the source database OCID as that of the source that you want to clone from.

• The cross tenancy cloning option is only available using the CLI or the Autonomous Database REST APIs. Cross tenancy cloning is not available using the Oracle Cloud Infrastructure Console.

  See Cross Tenancy and Cross-Region Cloning for more information.

• The cross tenancy cloning option does not support cloning with customer managed keys on the source. See Manage Encryption Keys on Autonomous Database for more information on customer managed keys.

Provides notes for resource management rules and performance data for a cloned database.

The following applies for resource management rules and performance data in a cloned database:

• During the provisioning for either a Full Clone or a Metadata Clone, any resource management rule changed by the user in the source database is carried over to the cloned database.

• For a cloned database, performance data for the time prior to the clone operation is not visible in the Database Dashboard card (under Monitor in Database Actions).

For more information on setting resource management rules, see Manage Runaway SQL Statements on Autonomous Database.

During the provisioning for either a Full Clone or a Metadata Clone, the optimizer statistics are copied from the source database to the cloned database.

The following applies for optimizer statistics for tables in a cloned database:

• Full Clone: loads into tables behave the same as loading into a table with statistics already in place.
• Metadata Clone: the first load into a table after the database is cloned clears the statistics for that table and updates the statistics with the new load.

For more information on Optimizer Statistics, see Optimizer Statistics Concepts.

Oracle Scheduler jobs from a source database are copied to the clone when you perform a clone operation. You can assure that cloned Oracle Scheduler jobs are disabled on the clone.

To disable Oracle Scheduler jobs on Autonomous Database instances that are cloned, you can define a trigger using the AFTER CLONE clause. To use the AFTER CLONE clause, define the trigger on the source database before you perform the clone operation.

For example:

CREATE OR REPLACE TRIGGER after_clone_instance
     AFTER CLONE 
     ON PLUGGABLE DATABASE
BEGIN 
-- Disable specific jobs or use a cursor to grab all scheduled jobs and disable them
     DBMS_SCHEDULER.DISABLE(name=> job_name);
END; 
/

See CREATE TRIGGER Statement for more information.

Note the following:

• The value for the DBA_SCHEDULER_WINDOWS.REPEAT_INTERVAL column is not copied to a cloned Autonomous Database instance.