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

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

  • ora-16202 : Skip procedure requested to replace statement
  • ora-09968 : unable to lock file
  • ora-19760 : error starting change tracking
  • ora-23454 : flavor string not defined for object group "string"."string"
  • ora-16174 : user requested thread/sequence termination of managed recovery
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-13752 : User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-29527 : created Java source string"string"
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-23381 : generated object for base object string.string@string does not exist
  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-25532 : MTTR specified is too large: string
  • ora-09217 : sfsfs: failed to resize file
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-16585 : illegal operation on a primary site
  • ora-12206 : TNS:received a TNS error during navigation
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-14111 : creation of a GLOBAL partitioned index on clustered tables is not supported
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-13790 : invalid value for time limit
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-08271 : sksabln: Buffer size not large enough for archive control string
  • ora-16145 : archival for thread# string sequence# string in progress
  • ora-29965 : The specified binding does not exist
  • ora-13067 : operator requires both parameters from the same topology
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-09988 : error while detaching SGA
  • ora-38603 : FI including & excluding cursor can only return one column
  • 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.