Disconnect a Refreshable Clone from the Source Database
Shows you the steps to disconnect a refreshable clone from the source database. When you disconnect a refreshable clone the refreshable clone is disassociated from the database that was the source database. This is a one time operation, is irreversible, and converts the database from a refreshable clone to a regular database.
There are several ways to find refreshable clones. See View Refreshable Clones for an Autonomous Database Instance for more information.
Perform the following prerequisite steps as necessary:
-
Open the Oracle Cloud Infrastructure console by clicking the
next to Oracle Cloud.
- From the Oracle Cloud Infrastructure left navigation list click either Autonomous Data Warehouse, Autonomous Transaction Processing, or Autonomous JSON Database depending on the workload type of your Autonomous Database.
-
On the Autonomous Databases page select your Autonomous Database from the links under the Display Name column.
Disconnect a refreshable clone from the source database and convert the refreshable clone to a read/write database as follows:
The Autonomous Database Lifecycle State changes to Updating. When the disconnect operation completes, the Lifecycle State changes to Available and the Mode shows Read/Write.
Notes for disconnecting from the source:
-
After a refreshable clone is disconnected from the source, the Autonomous Database Information area updates and does not show the Refreshable Clone information.
-
Disconnecting a refreshable clone from the source may fail if the source database has scaled down its storage and the refreshable clone has a larger amount of data than the source. In this case, you have the following options:
-
You may scale up the storage on the source database temporarily before disconnecting, and then scale the source back down after disconnecting.
-
Refresh the clone to a point where the scale down of storage occurred.
-