Oracle Cloud Infrastructure Documentation

Disable a Cross Region Standby Database

Disabling a cross-region Autonomous Data Guard standby database terminates the standby database. If you later add a cross-region Autonomous Data Guard standby, the system creates a new cross-region standby database.

You have two options to disable a cross-region Autonomous Data Guard standby:

You can update the cross-region disaster recovery type to use Backup-Based Disaster Recovery. This terminates the cross-region Autonomous Data Guard standby database and adds a cross-region backup copy peer.

You can terminate the cross-region Standby database.

Parent topic: Use Standby Databases with Autonomous Data Guard for Disaster Recovery

Update Cross-Region Standby to Use Backup-Based Disaster Recovery

You can update the disaster recovery type from cross-region Autonomous Data Guard standby database to cross-region Backup-Based Disaster Recovery. This terminates the cross-region Autonomous Data Guard standby database.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon 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 or Autonomous Transaction Processing.

  • On the Autonomous Databases page select your Autonomous Database from the links under the Display name column.

To change your disaster recovery type to use a cross-region backup-copy peer:

  1. On the Primary Role Autonomous Database, on the Autonomous Database Details page under Resources, select Disaster recovery.
  2. Access the remote standby.

    On the primary Autonomous Database instance the Disaster recovery information area shows the remote peer. The remote peer has the same display name as the primary database, with an "_Remote" extension.

    Under Peer Autonomous Database, click the link to access the cross-region peer.

  3. On the remote standby database, click Update disaster recovery under Disaster recovery on the Oracle Cloud Infrastructure Console.
  4. On the Update disaster recovery type page, select Backup-based disaster recovery.
  5. Click Submit.

    The Autonomous Database Lifecycle State changes to Updating.

    Note

    While you update the disaster recovery type, the primary database is available for read/write operations. There is no downtime on the primary database.

Autonomous Database generates a Change Disaster Recovery Configuration work request. To view the request, under Resources click Work Requests.

Terminate a Cross-Region Standby Database

Describes the steps to terminate a cross-region standby database.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon 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 or Autonomous Transaction Processing.

  • On the Autonomous Databases page select your Autonomous Database from the links under the Display name column.

To terminate a cross-region standby database:

  1. On the primary database, on the Autonomous Database Details page, under Resources select Disaster recovery.
  2. Access the remote standby.

    The Disaster recovery information area shows the Peer Autonomous Database. The remote standby database has the same display name as the primary database, with an "_Remote" extension.

    Under Peer Autonomous Database, click the link to access the cross-region peer.

  3. On the console for the remote standby database, from the More actions drop-down list, select Terminate.
    Description of adb_data_guard_terminate.png follows
  4. On the Terminate Autonomous Database page enter the database name to confirm that you want to terminate the cross-region standby database.
  5. Click Terminate Autonomous Database.

    While the standby database is terminating, the Lifecycle State changes to Terminating.

Note

If there is a local Autonomous Data Guard standby database, terminating the cross-region standby does not change the local disaster recovery option.

Note the following when your disaster recovery option includes a cross-region standby:

  • A cross-region standby database cannot be terminated from the primary database.

  • When there is a cross-region standby database, you must terminate the cross-region standby before you terminate the primary database. If you attempt to terminate the primary, the system shows the following message:

    Description of adb_data_guard_terminate_primary.png follows

    In this case, after you terminate the cross-region (remote) standby you can terminate the Primary role database.

After Autonomous Data Guard is disabled, terminate the database. See Terminate an Autonomous Database Instance for more information.

Verify Cross-Region Autonomous Data Guard is Disabled

Describes the steps to verify that an Autonomous Data Guard cross-region standby is disabled.

To verify that a cross-region Autonomous Data Guard standby database is disabled:

  1. On the primary database, on the Autonomous Database Details page under Resources, select Disaster recovery.
  2. Verify that either the disaster recovery type is changed to backup copy or the cross-region Autonomous Data Guard standby is terminated.

  • If you updated the disaster recovery type to use cross-region backup based disaster recovery, verify that the remote peer autonomous database DR Type shows backup copy.

    Description of adb_disable_verify_backup_copy.png follows

  • If you manually terminated standby database, verify that the cross-region standby count is 0 (that is there is no remote peer).

    Description of adb_disable_data_guard_verify.png follows