Building oracle11G DG in linux (4): subsequent verification

Building oracle11G DG in linux (4): subsequent verification

Environment

Name	Master Database	Slave Database
Host Name	Bjsrv	Shsrv
Software Version	RedHat performanise5.5, Oracle 11g 11.2.0.1	RedHat performanise5.5, Oracle 11g 11.2.0.1

Under the master database

$ Tail-f/u01/app/oracle/diag/rdbms/bjdb/TestDB12/trace/alert_TestDB12.log

For DG, you must enable the alarm log.

Slave Database

$ Tail-f/u01/app/oracle/diag/rdbms/shdb/trace/alert_shdb.log

4. Switch on the master database, slave database, and verification database.

Startup sequence: Enable the slave database first, then the master database, and enable the listener (lsnrctl start) of the master database );

Close sequence: first shut down the master database and then shut down the slave database.

Switch log verification Master/Slave Database

Master database operations

Process logic:

Master database switch log (3 times): master database switch log → form archive log → archive log will be sent to slave database → slave database receives archive log from master database → perform recover.

 

SQL>Altersystem switch logfile;

[Supplement]: The rediscovery area is enabled but not used.

View the alarm log in the slave database. Warning:

SQL>Show parameter recovery

After the query, it is found that the recovery region is not created on the slave database, so this small error is reported in the alarm log.

Oracle @ shsrv:/home/oracle>Mkdir/u01/app/oracle/fast_recovery_area

// Re-create the recovery area

If the file already exists, the system ignores the problem temporarily.

 

Recover on the slave Database

SQL>Recovermanaged standby database disconnect from session;

// Start the Media Recovery Process

View the process of archiving logs in the master database

Slave database alarm log information:

View log process in the master database

SQL>Selectmax (sequence #) from v $ archived_log where name is not null;

// You can see that the serial number of the archiving process in the master database is synchronized to that in the slave database.

Switch the master database again:

SQL>Altersystem switch logfile;

Slave database observation Alert Log:

 

Build DG successfully.

 

***************** *********

Statement:
Original works, from "Deep Blue blog" blog, allow reprint, reprint please be sure to indicate the source (http://blog.csdn.net/huangyanlong ).

The author has the right to pursue legal liability for copyright issues.