Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16629: Database reports a different protection level
from the protection mode.
- 2 Answers
- 22488 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-04081: trigger 'string' already exists
ORA-01482: unsupported character set
ORA-01910: TABLES keyword expected
PLS-00585: declared support library for opaque type is not a library
ORA-23387: replication parallel push dequeue error
ORA-02836: Unable to create temporary key file
NZE-28821: No input buffer provided.
ORA-21600: path expression too long
ORA-01606: gc_files_to_locks not identical to that of another mounted instance
ORA-00218: block size string of controlfile 'string' does not match DB_BLOCK_SIZE (string)
ORA-27489: unable to process job "string.string" from job class "string"
RMAN-06088: datafile copy string not found or out of sync with catalog
Oracle Errors 
