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 : 25-04-2017

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

  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-22309 : attribute with name "string" already exists
  • ora-19260 : XQ0040 - invalid namespace node in element constructor
  • ora-09776 : pws_look_up: access error on (Oracle helper) executable
  • ora-16506 : out of memory
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-29514 : class name contains illegal character
  • ora-16252 : Rebuild operation not permitted
  • ora-19036 : Invalid query result set in newContextFromHierarchy()
  • ora-24351 : invalid date passed into OCI call
  • ora-38307 : object not in RECYCLE BIN
  • ora-07408 : slbtpd: overflow while converting to packed decimal.
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-02226 : invalid MAXEXTENTS value (max allowed: string)
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-28538 : result set not found
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-12729 : invalid character class in regular expression
  • ora-24760 : invalid isolation level flags
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-19228 : XP0008 - undeclared identifier: prefix 'string' local-name 'string'
  • ora-00256 : cannot translate archive destination string string
  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-24769 : cannot forget an active transaction
  • ora-06319 : IPA: Remote maximum number of users exceeded
  • ora-07258 : spdcr: fork error, unable to create process.
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • 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.