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-22828: input pattern or replacement parameters exceed 32K size limit
NNL-00221: Statistic counter logging interval is now string
ORA-22307: operation must be on a user-defined type
TNS-00524: Current operation is still in progress
ORA-00367: checksum error in log file header
ORA-00346: log member marked as STALE
NZE-29114: Cannot import private key.
ORA-16133: Datafile string has incorrect terminal recovery stamp.
TNS-04234: Trace Assistant WARNING: won't decode TTC
ORA-06979: X.25 Driver: server cannot start oracle
NNO-00630: setting request-processing delay to number seconds
ORA-24307: invalid length for piece