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

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

  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-19732 : incorrect number of datafiles for tablespace string
  • ora-03231 : the INITIAL extent may not be deallocated
  • ora-25453 : invalid iterator: string
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-23370 : table string and table string are not shape equivalent (string)
  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-10927 : trace name context forever
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-15107 : missing or invalid ASM disk name
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-28107 : policy was disabled
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-30021 : Operation not allowed on undo tablespace
  • ora-29658 : EXTERNAL NAME clause is not compatible with its supertype
  • ora-14004 : missing PARTITION keyword
  • ora-16089 : archive log has already been registered
  • ora-19632 : file name not found in control file
  • ora-31676 : illegal value for number of workers, string
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-00451 : foreground process died unexpectedly
  • ora-40254 : priors cannot be specified for one-class models
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-16727 : resource guard cannot close database
  • ora-06430 : ssaio: Seals do not match
  • ora-13377 : invalid combination of elements with orientation
  • ora-02789 : Maximum number of files reached
  • 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.