ORA-16805: Change of LogXptMode property violates overall
protection mode.
- 1 Answers
- 2901 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The standby database resource guard rejected the
attempt to change the LogXptMode configuration property for
the standby database. The rejection was necessary to avoid
violating the overall protection mode for the configuration.
Action: If the LogXptMode configuration property must be
changed for the specified standby database, first downgrade
the overall protection mode for the broker configuration.
After that operation has completed, you will be able to
change the LogXptMode configuration property for the standby
database.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
NNL-00870: Update requests received: number
PCB-00006: Userid only used when SQLCHECK=FULL, userid ignored.
LPX-00273: failed to initialize TCP/IP
PCC-02374: SQLCHECK value exceeds command line value
ORA-26680: object type not supported
ORA-01669: standby database controlfile not consistent
ORA-31071: Invalid database username or GUID string
ORA-32123: Attribute number is out of range
ORA-06117: NETTCP: unable to create ORASRV: quota exceeded
ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
ORA-31082: invalid attribute "string" specified in declaration of "string"
LFI-00119: Unable to Abort an Unprotected file.
Oracle Errors 
