My Oracle Support Banner

PROTECTION_LEVEL being RESYNCHRONIZATION in a DATA GUARD environment (Doc ID 969002.1)

Last updated on FEBRUARY 14, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


Symptoms


The primary database runs in MAXIMUM AVAILABILITY protection mode. After loosing connectivity to the physical standby database, the protection level goes to RESYNCHRONIZATION, and remains at  RESYNCHRONIZATION even after the connectivity to the standby is reestablished. You wonder when the protection level will go back to MAXIMUM AVAILABILITY.

If you are using the Data Guard Broker and Fast-Start Failover, Fast-Start Failover will not be initiated as long as the Protection Level stays in 'RESYNCHRONIZATION'. The Data Guard Broker will report this Error:

ORA-16817: unsynchronized fast-start failover configuration

 

Changes

The network connection between the primary and the physical standby database is disconnected for some reason.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.