ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode

Cause : The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Make the modification before the database is opened by any instance.

update : 20-09-2017
ORA-16135

ORA-16135 - Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
ORA-16135 - Invalid LOG_ARCHIVE_CONFIG modification while in protected mode

  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-07275 : unable to send signal to process
  • ora-08176 : consistent read failure; rollback data not available
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-19916 : %s
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-06265 : NETNTT: break protocol error
  • ora-19102 : XQuery string literal expected
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-16151 : Managed Standby Recovery not available
  • ora-23436 : missing template authorization for user
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-06142 : NETTCP: error getting user information
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-07241 : slemrd: read error.
  • ora-23505 : Object "string"."string" is missing.
  • ora-13303 : failure to retrieve a geometry object from a table
  • ora-30360 : REF not supported with query rewrite
  • ora-16805 : change of LogXptMode property violates overall protection mode
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-31649 : Master process string violated startup protocol.
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-22339 : cannot alter to not final since its attribute column is substitutable
  • ora-12634 : Memory allocation failed
  • 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.