ORA-16629: Database reports a different protection level
from the protection mode.
Answers were Sorted based on User's Feedback
Answer / asha
In my case when i faced the error, my standby database was disabled.
Just enable the database from DGMGRL and wait for few mins,
DGMGRL> enable database 'xxxxxxxxxxxxxxx';
Enabled.
then you can see
Warning: ORA-16629: database reports a different protection level from the protection mode
will disappear and your primary and standby will sync automatically
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / guest
Cause: The actual protection level supported by the standby
database was different from the protection mode set on the
primary. This was likely caused by log transport problems.
Action: Check the database alert logs and Data Guard broker
logs for more details. Check the log transport status. Make
sure at least one standby log transport is supporting the
protection mode and that the network to the standby is working.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 3 No |
ORA-36610: (XSLMS00) Unable to locate a message file for product 'value' and facility 'value'.
VID-00714: internal error
ORA-06042: NETDNT: message receive failure
NNL-00281: Scheduled restart to occur in string
RMAN-10006: error running SQL statement: string
ORA-00369: Current log of thread string not useable and other log being cleared
LPX-00316: invalid value ~S for ~S attribute ~S
ORA-13206: internal error [string] while creating the spatial index
DRG-10550: illegal syntax for index, preference, source or section name
ORA-24128: partition name specified for a non-partitioned object
TNS-12674: Shared server: proxy context not saved
SQL*Loader-00406: If data is all generated, number to load cannot be ALL