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-04-2017
ORA-16805

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

  • ora-29265 : HTTP header not found
  • ora-29850 : invalid option for creation of domain indexes
  • ora-39957 : invalid warning category
  • ora-19629 : no files in specified archivelog SCN range
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-15205 : requested mirror side unavailable
  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-13228 : spatial index create failed due to invalid type
  • ora-21709 : cannot refresh an object that has been modified
  • ora-09352 : Windows 32-bit Two-Task driver unable to spawn new ORACLE task
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-22918 : specified column or attribute is not a VARRAY type
  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-02478 : merge into base segment would overflow MAXEXTENTS limit
  • ora-13510 : invalid RETENTION string, must be in the range (string, string)
  • ora-03207 : subpartitioned type must be specified for composite object
  • ora-14083 : cannot drop the only partition of a partitioned table
  • ora-13441 : GeoRaster metadata SRS error
  • ora-29831 : operator binding not found
  • ora-12611 : TNS:operation is not portable
  • ora-29364 : plan directive string, string already exists
  • ora-28367 : wallet does not exist
  • ora-14123 : duplicate NOREVERSE clause
  • ora-02337 : not an object type column
  • ora-23374 : object group "string"."string" already exists
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-07448 : ssarena: maximum number of shared arenas exceeded.
  • ora-12505 : TNS:listener does not currently know of SID given in connect descriptor
  • ora-27216 : skgfgsmcs: sbtinfo2 returned a malformed response
  • ora-09746 : smscre: shared memory attach address incorrect.
  • 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.