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 : 27-05-2017

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

  • ora-01112 : media recovery not started
  • ora-13761 : invalid filter
  • ora-24097 : Invalid value string, string should be non-negative
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-02036 : too many variables to describe with automatic cursor open
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-09819 : Number exceeds maximum legal value
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-16527 : unable to allocate SGA heap
  • ora-12821 : invalid value for INSTANCES
  • ora-13441 : GeoRaster metadata SRS error
  • ora-12203 : TNS:unable to connect to destination
  • ora-38487 : FUNCTION/PACKAGE/TYPE "string" not allowed in the expression
  • ora-01279 : db_files too large
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-03134 : Connections to this server version are no longer supported.
  • ora-24807 : LOB form mismatch
  • ora-28560 : error in configuration of agent process
  • ora-01531 : a database already open by the instance
  • ora-27006 : sbtremove returned error
  • ora-04013 : number to CACHE must be less than one cycle
  • ora-12708 : error while loading create database NLS parameter string
  • ora-24901 : handles belonging to different environments passed into an OCI call
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-02478 : merge into base segment would overflow MAXEXTENTS limit
  • ora-16557 : the database is already in use
  • ora-00070 : command string is not valid
  • ora-16661 : the standby database needs to be reinstated
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • 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.