Disable a Standby Database

Describes the steps to disable Autonomous Data Guard.

Note:

Disabling Autonomous Data Guard terminates the standby database. If you later enable Autonomous Data Guard, the system creates a new standby database.

To disable Autonomous Data Guard you individually disable the local standby database or terminate the cross-region standby database. If you have both a local standby and a remote standby, you first disable one and then the other. The order you disable multiple standby databases is not significant, either local first or remote first.

Disable a Local Standby Database

Describes the steps to disable a local 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, 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 disable a local standby database do the following:

  1. On the Autonomous Database Details page, under Autonomous Data Guard, in the Status field, click Disable.
  2. In the Disable Autonomous Data Guard dialog, select the local standby database.
  3. In the Disable Autonomous Data Guard dialog, enter the Autonomous Database name.
  4. In the Disable Autonomous Data Guard dialog, click Disable Autonomous Data Guard.

    While the local standby database is terminating the Lifecycle State changes to Updating.

    Autonomous Database generates the Disable Autonomous Data Guard work request. To view the request, under Resources click Work Requests.

After disabling the local standby, there are two possible results:

  • If there is no remote standby database, disabling the local standby database terminates the standby database and disables Autonomous Data Guard. See Verify Autonomous Data Guard is Disabled for more information.

  • If there is a cross-region standby database, disabling the local standby database terminates the local standby database but does not disable Autonomous Data Guard. In this case, to disable Autonomous Data Guard you must terminate the cross-region standby database. See Terminate a Cross-Region (Remote) Standby Database for more information.

Terminate a Cross-Region (Remote) 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, 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 terminate a cross-region (remote) standby database:

  1. On the Primary Region Autonomous Database, on the Autonomous Database Details page under Resources, select Autonomous Data Guard.
  2. Access the remote region Autonomous Database instance.

    On the Primary Region Autonomous Database instance the Autonomous Data Guard information area shows the Peer Autonomous Database. The remote standby database has the same name as the Primary Region database, with an "_Remote" extension.

    Under Peer Autonomous Database, click the remote standby database to access the cross-region Autonomous Database instance.

  3. On the remote Autonomous Database instance, on the Details page, from the More Actions drop-down list, select Terminate.
  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.

After you terminate the remote standby database, there are two possible results:

  • If there is no local standby database, terminating the cross-region standby database disables Autonomous Data Guard. See Verify Autonomous Data Guard is Disabled for more information.

  • If there is a local standby database, terminating the cross-region standby database terminates the remote database but does not disable Autonomous Data Guard. In this case, to disable Autonomous Data Guard you must disable the local standby database. See Disable a Local Standby Database for more information.

There are limitations for disabling when Autonomous Data Guard includes a cross-region standby, as follows:

  • A standby database in the remote region cannot be disabled from the primary database. If you click Disable on the primary and select a remote standby database, the system shows a message indicating that a cross-region standby database must be terminated from the remote region. The message includes a link you can use to access the remote standby instance.

    For example:

    Description of adb_data_guard_disable_remote.png follows
    Description of the illustration adb_data_guard_disable_remote.png
  • Disabling a database in the Remote region is not allowed when the standby in the remote region is running in the Primary role. Thus, after a switchover or a failover, if the database with the Primary role is in the Remote region, Disable is not active. When the Primary region database is in the Standby role, you must first switchover before you terminate the standby database.

  • When Autonomous Data Guard is enabled with a cross-region standby database, you must terminate the cross-region standby in the Remote region before you terminate the primary role database. If you attempt to terminate the primary, the system shows the following message:

    Description of adb_data_guard_terminate_primary.png follows
    Description of the illustration adb_data_guard_terminate_primary.png

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

  • You cannot terminate the Primary role database when it is running in the Remote region. A switchover or a failover operation is not meant to be permanent. In this case, to disable Autonomous Data Guard you take the following steps:

    1. Perform a switchover so that the Primary role database is running in the Primary region.
    2. After the switchover, terminate the standby database in the Remote region. See Terminate a Cross-Region (Remote) Standby Database for more information.
    3. If there is a local standby database, disable the local standby database. See Disable a Local Standby Database for more information.

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

Verify Autonomous Data Guard is Disabled

Describes the steps to verify Autonomous Data Guard is disabled.

To verify that Autonomous Data Guard is disabled:

  1. On the Autonomous Database Details page under Resources, select Autonomous Data Guard.
  2. Verify the standby database count is 0 and that the Autonomous Data Guard area shows None Available.

If a local or a cross-region standby database remains and you want to terminate it, individually terminate the local or the cross-region standby: