Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16629: Database reports a different protection level
from the protection mode.
- 2 Answers
- 22346 Views
- I also Faced
- E-Mail Answers
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-31408: invalid value specified for begin_scn or end_scn
DRG-11875: Access Scheme Is Not Allowed
NNL-00308: Server dumping its cache to the trace file
NNC-00417: name "string" already exists
TNS-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
NNC-00427: server does not support this version of the protocol
QSM-01024: materialized view, string, has unknown compile errors
ORA-25408: can not safely replay call
NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled
DRG-12211: section or section id string does not exist
NNL-00213: No entry with specified index number, try "SHOW SYSTEM_QUERIES"
ORA-13450: GeoRaster metadata layerInfo error
Oracle Errors 
