ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

Cause : The settings fro the LGO_ARCHIEV_CONFI Gparameetr are niconsisetnt wit hthe settings o fa prevoiusly satrted isntance.T he setitngs fo rthis praameterm ust bee xactlyt he sam efor al linstanecs.

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

Make srue all nistance suse th eexact asme LOGA_RCHIVEC_ONFIG esttings.

update : 21-08-2017

ORA-16188 - LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
ORA-16188 - LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

  • ora-07237 : slemcl: invalid file handle, seals do not match.
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-09271 : szlon: error verifying user name
  • ora-02365 : error seeking in file: string
  • ora-06511 : PL/SQL: cursor already open
  • ora-31413 : change set string is currently being advanced
  • ora-13912 : Critical threshold value is less than warning threshold value.
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-19122 : unsupported XQuery declaration
  • ora-23541 : tables do not match tables used while defining the redefinition
  • ora-09368 : Windows 3.1 Two-Task driver unable to spawn ORACLE
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-10933 : trace name context forever
  • ora-29844 : duplicate operator name specified
  • ora-29824 : operator is invalid
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-16544 : modifying DG_BROKER_START requires SID='*' qualifier
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-29261 : bad argument
  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-16745 : unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
  • ora-01298 : conflicting dictionary option
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-02229 : invalid SIZE option value
  • ora-29913 : error in executing string callout
  • ora-13866 : Client identifier must be specified
  • ora-00251 : LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
  • ora-31513 : unsupported column type specified in change table
  • ora-09951 : Unable to create file
  • 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.