You can enable Autonomous Data Guard when Autonomous Database is available (Lifecycle State shows Available).
Note:To enable Autonomous Data Guard you must have adequate available resources and by enabling Autonomous Data Guard you must not exceed your Tenancy or compartment limits for CPU and Storage.
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 menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
On the Autonomous Databases page select your Autonomous Database from the links under the Display Name column.
To enable Autonomous Data Guard do the following:
- On the Autonomous Database Details page, under Autonomous Data Guard, click Enable in the Status field.
- In the Region field, select a region.
- To create a local standby database, select the Current Region. To
create a cross-region standby database, select a different region.The region list shows the current region for a local standby and the available remote regions where you can create a cross-region standby.
- If you select a different region, Autonomous Database shows the Select a compartment list. From this list, choose a compartment for the cross-region standby.
Note:When you enable Autonomous Data Guard, the list of available Standby databases only shows a remote region if your tenancy is subscribed to the remote region (you must be subscribed to the paired remote region for the region where you are enabling Autonomous Data Guard).
- To create a local standby database, select the Current Region. To create a cross-region standby database, select a different region.
- Click Enable Autonomous Data Guard.
The Autonomous Database Lifecycle State changes to Updating. In the Resources area with Autonomous Data Guard selected, the State field shows Provisioning.
After some time, the Lifecycle State shows Available and the standby database provisioning continues.
Note:While you enable Autonomous Data Guard the primary database is available for read/write operations. There is no downtime on the primary database.
When provisioning completes, on the Autonomous Database Details page under Autonomous Data Guard, the Role field shows Primary with a link Switchover that you can click to perform a switchover.
Description of the illustration adb_peer_state_data_guard.png
If you enable a remote standby, there is an additional Region field that shows Primary.
Description of the illustration adb_peer_state_cross_data_guard.png
If you enable a cross-region standby, the standby database created in the remote region has the same display name as the primary database, with the extension, "_Remote". The standby database display name and a link to the standby database shows under the Peer Autonomous Database column when you click Autonomous Data Guard under Resources.
Notes for enabling Autonomous Data Guard:
Autonomous Database generates the Enable Autonomous Data Guard work request. To view the request, under Resources click Work Requests.
After you enable Autonomous Data Guard with a remote standby, download a new instance wallet. The instance wallet file you download from the primary database contains connection strings for both the primary region and the remote region database. The same instance wallet works after you switchover or failover to the remote region standby.
The order of the connections strings in the instance wallet file impacts the database connection time. For best performance, use an instance wallet file downloaded from the region in which the current Primary instance resides.
While you enable Autonomous Data Guard, when the Lifecycle State field shows Updating, the following actions are disabled for the primary database:
Move Resource. See Move an Autonomous Database to a Different Compartment for information on moving an instance.
Stop. See Stop Autonomous Database for information on stopping an instance.
Restart. See Restart Autonomous Database for information on restarting an instance.
Restore. See Restore and Recover your Autonomous Database for information on restoring.