Standby Instance Crash or Failed to Startup with ORA-16188 (Doc ID 1580482.1)

Last updated on APRIL 19, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 12.1.0.1 [Release 11.1 to 12.1]
Information in this document applies to any platform.

Symptoms

In RAC environment if log_archive_config made to null '' on one node then the other node crash with , "ORA-16188". Startup of node 2 also will fail with ORA-16188.

 

-------sample Alert log-----------

In the alert log we are seeing:
WARNING: The 'LOG_ARCHIVE_CONFIG' init.ora parameter settings
are inconsistent with another started instance. This may be
caused by the 'DB_UNIQUE_NAME' init.ora parameter being specified
differently on one or more of the other RAC instances; the
DB_UNIQUE_NAME parameter value MUST be identical for all
instances of the database.
Errors in file /u02/diag/rdbms/nprod/nprod1/trace/nprod1_lgwr_26567.trc:
ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
Wed Jul 24 07:07:20 2013

 

Example,

Alter system set log_archive_config='' scope=both sid='*'
 
Now try to restart the only one node we will get 
ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started 
instance
Errors in file /oracle/app/admin/test/bdump/test2_lgwr_29682.trc:
ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started 
instance
LGWR: terminating instance due to error 16188
 
and instance will be terminated.
 
++ Problem is v$dataguard_config is not updated between instances 






Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms