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 |
TNS-00123: Unable to perform a listen on configured ADDRESS(es)
PCC-02359: Identifier specifying ARRAYLEN must be a 4-byte integer
ORA-39030: invalid file type string
ORA-13517: Baseline (id = string) does not exist
ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous memory
ORA-00276: CHANGE keyword specified but no change number given
ORA-32125: Attribute type is not appropriate
LPX-00305: missing token
ORA-07453: requested resource manager plan schema does not contain OTHER_GROUPS
DRG-10853: Catsearch does not support this operator
NNL-01041: Data stream open failures: number
ORA-26710: incompatible version marker encountered during Capture