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-19804: cannot reclaim string bytes disk space from string limit
NNO-00252: invalid administrative region parameter string value "string"
ORA-06140: NETTCP: no such user
ORA-03280: invalid DATAFILE filename specified
ORA-01725: USERENV('COMMITSCN') not allowed here
ORA-03233: unable to extend table string.string subpartition string by string in tablespace string
PCC-02327: struct or struct pointer required
IMG-00579: extra quantize argument
NNO-00268: warning: configuration database is not used, using checkpoint data instead
ORA-23379: connection qualifier "string" is too long
ORA-01906: BACKUP keyword expected
ORA-15091: operation incompatible with open handle in this session