ORA-16805: change of LogXptMode property violates overall protection mode

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 - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

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.

update : 21-07-2017
ORA-16805

ORA-16805 - change of LogXptMode property violates overall protection mode
ORA-16805 - change of LogXptMode property violates overall protection mode

  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-08270 : sksachk: Illegal archival control string
  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-16512 : parameter exceeded maximum size limit
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-08235 : smsget: listener not on this node
  • ora-07392 : sftcls: fclose error, unable to close text file.
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-23432 : master site string already exists
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-24347 : Warning of a NULL column in an aggregate function
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-19024 : Cursor expression must be named
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-06907 : CMX: error during connect confirmation
  • ora-22319 : type attribute information altered in ALTER TYPE
  • ora-09911 : Incorrect user password.
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-02009 : the size specified for a file must not be zero
  • ora-14126 : only a may follow description(s) of resulting partitions
  • ora-01668 : standby database requires DROP option for offline of data file
  • ora-06765 : TLI Driver: error awaiting orderly release
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-01062 : unable to allocate memory for define buffer
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.