Inconsistent parameters of two nodes in db_file_name_convert in ADG Environment-- the simplest way to deal with it

Problem scenario: ADG environment, in which Node 2 is down, and the ADG parameters db_file_name_convert and log_file_name_convert take effect after the bad node is restarted, resulting in inconsistency between the two node parameters. Node 2 reads parameters in spfile, and node 1 uses parameters in memory. The parameters of the two nodes are not consistent, so the Node 2 instance is started.

1:

Node 1 is good:

Node 1:

Create the pfile in example 1: create pfile='/home/oracle/pfile.ora' from spfile

Parameter values in spfile:

* .db_file_name_convert='/oradata/sunecm/','+DATA/sunecm/datafile/','/oradata/sunecm/','+DATA/sunecm/tempfile/'

* .log_file_name_convert='/oradata/sunecm/','+DATA/sunecm/onlinelog/','/oradata/sunecm/','+FRA/sunecm/onlinelog/'

Or view the value in memory in node 1:

Show parameter db_file_name_convert

Show parameter log_file_name_convert

You can see that the two values are different from the values in the parameter file.

2:

The easiest way: change the value of spfile to the value of memory in node 1, so that node 2 gets up and then changes it back.

At Node 1

Alter system set db_file_name_convert= (value of node 1show parameter db_file_name_convert) scope=spfile

Alter system set log_file_name_convert= (value of node 1show parameter log_file_name_convert) scope=spfile

3:

Start Node 2 database instance

4:

The value scope=spfile created by pfile in node 1 alter system set instance 1