Automatic Failover with a Standby Database

After you enable Autonomous Data Guard, the system monitors the primary instance and automatically fails over to a local standby database in certain scenarios. If automatic failover is not possible, you have the option to perform a manual failover. Automatic failover does not apply to a cross-region standby.

Autonomous Database automatically fails over to a local standby database as follows:

  • When the primary database becomes unavailable and users are not able to connect, Autonomous Data Guard automatically fails over to a local standby database if a local standby database is available, based on the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) targets. See Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for more information.

  • Autonomous Data Guard performs automatic failover to a local standby database when a local standby database is available and the system can guarantee zero data loss, as specified by the Recovery Point Objective (RPO) target. If this target cannot be met then automatic failover does not succeed and you have the option to perform manual failover. See Autonomous Data Guard Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for more information.

  • After automatic failover to a local standby database completes, Autonomous Database creates a new local standby database for you.

    Autonomous Data Guard for a particular standby, either local or remote, is not enabled while the system is provisioning the new standby database. After Autonomous Data Guard completes the provisioning step for the standby database and it becomes available, you then have a new standby database with Autonomous Data Guard enabled on it.
  • After automatic failover completes, Autonomous Database reports the time of the last failover when you hover over the tooltip icon in the Role field.

If the primary database has failed or is unreachable and the conditions for Autonomous Data Guard automatic failover have not been met, then Oracle Cloud Infrastructure console shows a banner indicating that automatic failover did not succeed, provides a reason, such as possible data loss, and provides a link for you to initiate manual failover. See Manual Failover with a Standby Database for more information.

Note:

Autonomous Data Guard automatic failover is disabled when the Lifecycle State is either: Restore in Progress or Upgrading.