After doing a package install the 2 node RAC database running on 11.1.0.7.0 was brought up .One instance came up fine but the other instance was not coming up and throwing the following error.
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/shas/shas2/trace/swprd2_lgwr_5292.trc:
--After looking at the paratemet log_archive_config it was null and also the DB_UNIQUE_NAME was same across 2 nodes.The we checked the view "Select * from v$dataguard_config" and identified that it has non identical entry from the other node.I used following steps to resolve the issue:
you can reset this parameter and bring the instance.
Just mount the instance - problematic one
alter system set log_archive_config='dg_config=(nodg_config)' scope=both sid='*';
ORA-03113: end-of-file on communication channel
Process ID: 20194
Session ID: 1655 Serial number: 5
WARNING: The 'LOG_ARCHIVE_CONFIG' init.ora
parameter settingsProcess ID: 20194
Session ID: 1655 Serial number: 5
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/shas/shas2/trace/swprd2_lgwr_5292.trc:
--After looking at the paratemet log_archive_config it was null and also the DB_UNIQUE_NAME was same across 2 nodes.The we checked the view "Select * from v$dataguard_config" and identified that it has non identical entry from the other node.I used following steps to resolve the issue:
you can reset this parameter and bring the instance.
Just mount the instance - problematic one
alter system set log_archive_config='dg_config=(nodg_config)' scope=both sid='*';
No comments:
Post a Comment