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-14622: Value string already exists in subpartition string
NNF-00110: no values exist
ORA-01673: data file string has not been identified
ORA-31081: name not specified for global declaration
ORA-16177: media recovery is not required
TNS-01180: Missing listener object string in Directory Server
ORA-00345: redo log write error block string count string
ORA-13349: polygon boundary crosses itself
RMAN-06075: datafile string does not belong to this database
PLS-00118: Duplicate group-by clause in table expression
ORA-32108: max column or parameter size not specified
NCR-01011: NCRS: Send message failure.