Refreshable Clone Notes

Lists limitations and notes for Autonomous Database refreshable clones.

  • Always Free Autonomous Databases do not support refreshable clones.

  • Autonomous Database does not support using customer-managed encryption keys with a refreshable clone. You cannot create a refreshable clone from a source database that uses customer-managed encryption keys. Additionally, you cannot switch to a customer-managed encryption key on a source database that has one or more refreshable clones.

  • You cannot create a cascading series of refreshable clones. Thus, a refreshable clone cannot be created from another refreshable clone.

  • You cannot backup or restore a refreshable clone.

  • The ADMIN password for a refreshable clone is inherited from the source database. If you want to change the ADMIN password for a refreshable clone you must change the ADMIN password on the source database, and then refresh the clone for the ADMIN password on the clone to come into effect.

  • Oracle APEX (APEX) URLs do not work in a refreshable clone read-only database and the APEX URLs are disabled in the Oracle Cloud Infrastructure Console and in the Database Actions APEX and APEX Workspaces cards. APEX URLs are enabled for a read/write database when a refreshable clone is disconnected from the source.

  • Oracle Machine Learning is disabled in a refreshable clone read-only database. The OML User Administration URLs are disabled in the Oracle Cloud Infrastructure Console and on the Database Actions Launchpad.

  • Oracle Data Safe is not supported for a refreshable clone instance. The Data Safe data in the refreshable clone's source database, for example user registration, data masking, and so on are available and Data Safe can be enabled when a refreshable clone is disconnected from the source.

  • When you scale up or scale down the storage on the source Autonomous Database instance for a refreshable clone, the change is immediately reflected in the database console and in the billing for the refreshable clone. When the refreshable clone is refreshed to a refresh point after the scale up or down operation, the system makes a corresponding change to the refreshable clone storage (scaling up or scaling down the refreshable clone storage to match the source database).

  • You cannot use the rename operation on a refreshable clone instance or on a database that is the source for a refreshable clone.

  • You cannot set the patch level when you create a refreshable clone. A refreshable clone has the same patch level as the source database. See Set the Patch Level for more information.

  • Automatic Workload Repository (AWR) data and reports are not available for refreshable clones. In addition, the graphs that rely on AWR data are not available, including the following graphs:

    • The Running SQL statements graph on the Overview tab shown on the Database Monitor card in Database Actions.

    • The SQL statement response time graph on the Overview tab shown on the Database Monitor card in Database Actions.

    • The Time period graphs on the Monitor tab shown on the Database Monitor card in Database Actions.

    • The Performance Hub graph data older than one hour is not available.

  • For an Oracle Autonomous JSON Database (workload type JSON Database), note the following when reconnecting to the source database:
    • If, after you disconnect the refreshable clone, you promote both the clone and the source to Oracle Autonomous Transaction Processing (workload type Transaction Processing), you can reconnect the database to the source.

    • If after you disconnect the refreshable clone, you promote the source database to Oracle Autonomous Transaction Processing (workload type Transaction Processing) and do not promote the disconnected clone, the disconnected clone must be promoted to before you perform the reconnect operation.

    • If after you disconnect the refreshable clone, you promote the disconnected database to Oracle Autonomous Transaction Processing (workload type Transaction Processing), you can still reconnect to the source but the reconnected database remains in the promoted state.

    See Promote to Autonomous Transaction Processing for more information.