Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

3. Copy the second RAC database instance pfile and password file from the source site to the
second RAC database instance node in the target disk.
In this example, run the following commands from the second node in site1:
# cd /opt/app/oracle/product/11.1.0/db_1/dbs
# rcp -p inithrdb2.ora <site2_node2>:$PWD
# rcp -p orapwhrdb2 <site2_node2>:$PWD
The -p option retains the permissions of the file.
4. Set up the second RAC database instance on the target disk site.
In this example, run the following commands from the second node in site2:
# cd /opt/app/oracle/product/11.1.0/db_1/dbs
# chown oracle:oinstall orapwhrdb2
# chown oracle:oinstall inithrdb2.ora
5. Create the directory for the database (in this example “hrdb”) that is replicated at the target
disk site, in the Oracle admin directory.
# cd /opt/app/oracle
# rcp -r admin/hrdb <site2_node1>:$PWD
# rcp -r admin/hrdb <site2_node2>:$PWD
6. Run the following command at the remote site.
# chown -R oracle:oinstall /opt/app/oracle/admin/hrdb
7. Log in at any of the nodes in the remote site using the oracle user credentials.
# su – oracle
8. Configure a listener for the database on this site using the Oracle Network Configuration
Assistant (NETCA).
9. Copy the tnsnames.ora file from the remote CRS sub-cluster and modify it to fit the local
environment.
In this example, the file contents will appear as follows:
# rcp <site1_node1>:$ORACLE_HOME/network/admin/tnsnames.ora
<site2_node1>:$ORACLE_HOME/network/admin/tnsnames.ora
# rcp <site1_node2>:$ORACLE_HOME/network/admin/tnsnames.ora
<site2_node2>:$ORACLE_HOME/network/admin/tnsnames.ora
10. Edit the tnsnames.ora file on the nodes at the target disk site and modify the HOST =
keywords to suit the target disk site environment.
In this example, you must edit the tnsnames.ora file on every node in this site.
11. Register the database with the CRS sub-cluster on remote site.
# srvctl add database -d hrdb -o /opt/app/oracle/product/11.1.0/db_1/
# srvctl add instance -d hrdb -i hrdb1 -n <site2_node1>
# srvctl add instance -d hrdb -i hrdb2 -n <site2_node2>
After registering the database with the CRS sub-cluster on the remote site, you can run the srvctl
status command to view the health of the database.
Configuring the Site Controller package
The procedure to configure the Site Controller Package is identical to the procedure in configuring
Oracle RAC in SADTA.
Configuring Oracle RAC database with ASM in a SADTA 125