ORA-16629: Database Reports A Different Protection Level From The Protection Mode (Doc ID 2951193.1)

Last updated on JUNE 06, 2023

Applies to:

Symptoms

ORA-16629: database reports a different protection level from the protection mode

1. SWITCHOVER_STATUS shows:

SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
 
SWITCHOVER_STATUS
--------------------
RESOLVABLE GAP  <<<<<<<<<<<<<<<<<<<<<<<

2. Below query also shows "RESOLVABLE GAP"

SQL> select status,DEST_ID,TYPE,ERROR,GAP_STATUS,SYNCHRONIZED,SYNCHRONIZATION_STATUS,RECOVERY_MODE from V$ARCHIVE_DEST_STATUS where STatus <> 'INACTIVE';
 
STATUS DEST_ID TYPE ERROR GAP_STATUS SYN SYNCHRONIZATION_STATUS RECOVERY_MODE
--------- ---------- ---------------- -------------------- ------------------------
VALID 1 LOCAL NO CHECK CONFIGURATION IDLE
VALID 2 PHYSICAL RESOLVABLE GAP NO DESTINATION HAS A GAP MANAGED REAL TIME APPLY    <<<<<<<<< RESOLVABLE GAP
 
3. Protection level shows "RESYNCHRONIZATION"

SQL> select name, protection_mode, protection_level from v$database;
 
NAME PROTECTION_MODE PROTECTION_LEVEL
--------- -------------------- --------------------
POHK3CSL MAXIMUM AVAILABILITY RESYNCHRONIZATION  <<<<<<<<<<<<<<<<<<

4. Broker validate database command shows "Not ready for Switchover" although both primary and standby is in sync.

DGMGRL> validate database verbose <standby_db_name>
 
  Database Role: Physical standby database
  Primary Database: prim_db
 
  Ready for Switchover: No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
  Ready for Failover: Yes (Primary Running)
 

Changes

Cause

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