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 : 26-07-2017

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

  • ora-40206 : invalid setting value for setting name string
  • ora-12634 : Memory allocation failed
  • ora-39031 : invalid filter name string
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-32806 : value for string is too long, maximum length is string
  • ora-22974 : missing WITH OBJECT OID clause
  • ora-23441 : object does not exist for refresh group template
  • ora-13441 : GeoRaster metadata SRS error
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-16539 : task element not found
  • ora-08319 : sllfsk: Error reading file
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-22982 : cannot create sub-view under this view
  • ora-30737 : cannot create subtable of a type which is not a subtype of the type of the supertable
  • ora-16121 : applying transaction with commit SCN string
  • ora-09835 : addCallback: callback port is already in a set.
  • ora-00376 : file string cannot be read at this time
  • ora-01638 : parameter string does not allow ORACLE version string to mount cluster database
  • ora-02739 : osncon: host alias is too long
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-30036 : unable to extend segment by string in undo tablespace 'string'
  • ora-12218 : TNS:unacceptable network configuration data
  • ora-13006 : the specified cell number is invalid
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-31038 : Invalid string value: "string"
  • ora-02783 : Both post and wait functions were not specified
  • ora-07747 : slemrd: $READ failure
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • 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.