My Oracle Support Banner

DGMGRL Reports Warning ORA-16629, DataGuard Remains In Protection_Level "RESYNCHRONIZATION" After Upgrade to 19.16 DBRU (Doc ID 2897795.1)

Last updated on JANUARY 03, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 19.16.0.0.0 and later
Information in this document applies to any platform.

Symptoms

After upgraded database to 19.16 DBRU, DataGuard configuraiton which is in MAXIMUM AVAILABILITY protection_mode started reporting the following symptoms:

1. The dataguard broker shows status of production database as Warning: ORA-16629: database reports a different protection level from the protection mode.

2. DGMGRL>Validate database <standby> shows Ready for Switchover: No and datagaurd broker log shows there is resolvable gap.

3. DGMGRL>Show database <standby> :  shows that standby is in sync and there is no gap.

4. Standby database receives and does apply the redo logs, but it never gets back to protection_level MAXIMUM AVAILABILITY, protection_level=RESYNCHRONIZATION.

5. In alert_log, there is a message reported "Changing standby controlfile to RESYNCHRONIZATION level" but the message "Changing standby controlfile to MAXIMUM AVAILABILITY level" never shows up.

However, Primary and Standby database are in the sync and no transport and apply lag reported.

Changing the protection_mode to maximum performance caused  ORA-16629 error to not occur away, and protection_level=maximum performance. 

Changing the protection_mode back to maximum availability the ORA-16629 error is returned, and protection_level=RESYNCHRONIZATION. 

Changes

 Applied 19.16.0.0.220719 (July 2022) DB Release Update (DB RU)

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.