ORA-16629 database reports a different protection level from the protection mode
(Doc ID 1319903.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 18.104.22.168 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary Database Name: CHICAGO
Standby Database Name: BOSTON
Configuration Name: ORCL_EXAMPLE
a) 22.214.171.124 Primary with a Physical standby operating in MaxAvailability Mode managed via Data Guard Broker
b) SYNC redo transport & Standby Redo logs are configured
c) standby's standby redo logs (SRL) size don't match with Primary's Online Redo Logs size (ORL)
d) standby's v$standby_log.status shows "UNASSIGNED" for all SRL Group,
It confirms that we don't use SRL
e) Redo transport & Redo Apply does not get hampered
f) Primary & standby v$database.protection_level shows "RESYNCHRONIZATION"
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