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-28120: driving context already exists
ORA-24786: separated transaction has been completed
ORA-04029: error ORA-string occurred when querying stringstringstring
ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
ORA-12094: error during online redefinition
ORA-32134: Cannot assign LOBs
ORA-01155: the database is being opened, closed, mounted or dismounted
SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.
ORA-24418: Cannot open further sessions.
PLS-00374: illegal EXIT statement; it must appear inside the loop labeled 'string'
ORA-16159: Cannot change protected standby destination attributes
ORA-01588: must use RESETLOGS option for database open