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-13015: the window definition is not valid
ORA-30376: prevent sharing of a parsed query of an explain rewrite session
ORA-24907: invalid pair of callback and recepient protocol attributes
NNL-00266: Round trip time is string
ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory
ORA-21525: attribute number or (collection element at index) string violated its constraints
ORA-30334: illegal dimension level name
ORA-36341: (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
ORA-19619: cannot call restoreValidate after files have been named
ORA-07499: spglk: Cannot reschedule.
NID-00601: Internal Error - [number] [string] [number] [number]
ORA-28172: distinguished name not provided by proxy