Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16629: Database reports a different protection level
from the protection mode.
- 2 Answers
- 22364 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-28515: cannot get external object definitions from string
ORA-29828: invalid name for implementation type
ORA-39139: Data Pump does not support XMLSchema objects. string will be skipped.
ORA-27039: create file failed, file size limit reached
ORA-00108: failed to set up dispatcher to accept connection asynchronously
AMD-00116: PROCEDURE string, read error
PLS-00375: illegal GOTO statement; this GOTO cannot branch to label 'string'
ORA-02269: key column cannot be of LONG datatype
ORA-34296: (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
PLS-00950: In this version, PL/SQL tables can not be used in this SQL statement.
ORA-22954: This multiset operation is not supported for this element type.
ORA-13123: invalid <TOPOLOGY> name specified
Oracle Errors 
