Configure the replicuard environment for the oracle RAC Database

The RAC feature in ORACLE protects instances, while the RMAN feature maintains data, while the replicuard feature is that instances are connected with data in a "guaranteed" manner, these three features work together to build a secure, reliable, and highly available ORACLE database platform to a certain extent.

Previous articles have described RAC creation, RMAN management, and Dataguard feature applications. This article will demonstrate how to create Dataguard configurations for the RAC database through practice.

I. complete preparations

The configuration of the replicasuard environment is similar to the relationship between two people (Primary db + Standby db. However, before the two were launched, it was very necessary to pick up the house and pick up the house. At the very least, we had to look in the mirror and see if our eyes were sharp enough and our waist was not hibiscus enough. We had to push it forward for three hundred years, we will continue to push for three hundred years, with a total of six hundred years of thought-making.

I personally think that DBA is a very rigorous position. Therefore, it is also required that people engaged in this job should be as rigorous as possible to prepare for this issue, in order to make subsequent operations more secure. For the creation of the replicuard environment, this preparation is not complicated. It should be environment initialization. If you have read the previous three thought notes-learn replicuard step by step, you can skip this step of preparation.

The environment is set as follows:

Primary:

Db_unique_name: jssdb

IP: 192.168.10.11/12

DB Version: 10.2.0.4

Storage: ASM

Standby:

Db_unique_name: jssstd

IP: 192.168.10.101

DB Version: 10.2.0.4

Storage: local disk

The preparation is as follows:

Standby end $ ORACLE_BASE/admin/to create the corresponding trace directory;

Modify the listener. ora and tnsnames. ora files on the Primary and Standby end, configure the listener and the local network service name, and ensure that the two ends can communicate with each other through tnsping;

The Primary end is in the archiving and force logging status;

Query and record the paths of the Primary files on the Primary end. On the one hand, it is used for subsequent path conversion, and on the other hand, it is omitted when copying files. The statement is as follows:

SQL> select name from v $ datafile;

NAME

Bytes --------------------------------------------------------------------------------------------------------

+ ASMDISK1/jssdb/datafile/system.260.702131683

+ ASMDISK1/jssdb/datafile/undotbs1.259.702131695

+ ASMDISK1/jssdb/datafile/sysaux.266.702131697

+ ASMDISK1/jssdb/datafile/undotbs2.258.702131705

+ ASMDISK1/jssdb/datafile/users.257.701_1709

+ ASMDISK1/jssdb/datafile/jsstbs.269.703779631

6 rows selected.

SQL> select name from v $ tempfile;

NAME

Bytes ----------------------------------------------------------------------------------------------------------

+ ASMDISK1/jssdb/tempfile/temp.265.702131701

SQL> select member from v $ Logfile;

MEMBER

Bytes ---------------------------------------------------------------------------------------------------------

+ ASMDISK1/jssdb/onlinelog/group_1.263.702131679

+ ASMDISK1/jssdb/onlinelog/group_2.261.702131681

+ ASMDISK1/jssdb/onlinelog/group_3.256.703672257

+ ASMDISK1/jssdb/onlinelog/group_4.268.703672257