ORA-16629: Database reports a different protection level
from the protection mode.
- 2 Answers
- 21302 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-32592: all columns in log group can not be no log columns
ORA-38483: invalid FUNCTION/PACKAGE/TYPE name: "string"
PLS-00708: Pragma string must be declared in a package specification
RMAN-08517: backup piece handle=string recid=string stamp=string
SQL*Loader-00524: partial record found at end of datafile (string)
QSM-01103: there is a remote table, string, referenced in the query
IMG-02011: 2FF11 - unsupported image format conversion specified
ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile
ORA-30332: container table already in use by other summary
ORA-32623: incorrect use of MODEL PRESENT* functions
DRG-50940: parser not parsed
ORA-32012: failure in processing system parameters from restored SPFILE
Oracle Errors 
