Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to solve the problem of Dataguard log transmission status monitoring in Oracle. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

The synchronization of master and slave databases in ORACLE DATAGUARD mainly depends on the transfer of logs to the standby database, and the application logs or archives of the standby database. When GAP appears in log transfer between master and slave, the slave will no longer synchronize with the master. Therefore, it is necessary to monitor the log transmission status to ensure that there is no GAP between the master and slave databases, or to deal with the GAP in a timely manner. In addition to viewing the log synchronization in the alarm log, you can also monitor the log transfer status by viewing the relevant views.

1. Master and slave databases view the current log status

SELECT SEQUENCE#,STATUS FROM V$LOG

2. Prepare the database to view the synchronization of RFS receiving logs and MRP application logs.

SELECT PROCESS, SEQUENCE#, STATUS, DELAY_MINS FROM V$MANAGED_STANDBY

3. Check whether the standby database is synchronized with the main database.

SELECT SEQUENCE#,STATUS FROM VolutionLOGX select ARCHIVED_THREAD#,ARCHIVED_SEQ#,APPLIED_THREAD#,APPLIED_SEQ# FROM V$ARCHIVE_DEST_STATUS

4. Prepare the database to view the archived REDO

SELECT REGISTRAR,CREATOR,THREAD#,APPLIED,SEQUENCE#,FIRST_CHANGE#,NEXT_CHANGE#, COMPLETION_TIME FROM V$ARCHIVED_LOG

5. Prepare the database to view the REDO that has been applied

SELECT THREAD#,SEQUENCE#,FIRST_CHANGE#,NEXT_CHANGE# FROM V$LOG_HISTORY

6. Check whether there is a GAP in the main and standby databases.

SELECT STATUS,GAP_STATUS FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2

Prepare the library for viewing

SELECT * FROM V$ARCHIVE_GAP

Master and standby database query exception information

SELECT T.STATUS,T.ERROR FROM V$ARCHIVE_DEST T

[summary of experiments]

Through the above six methods, you can monitor the log transfer between the master and backup databases.

If there is a generation gap (GAP) in log transmission, you need to troubleshoot the problem in time, and manual GAP measures can be taken if necessary.

For 6

Query the path and name of the missing log in the main library

SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND SEQUENCE# BETWEEN 99 AND 109

Copy to the appropriate directory of the standby library

Oracle@p1a:/home/oracle/arch > scp orcl_53716_710350416.log ss1:/home/oracle/archive_gap/

Register the log file manually.

SQL > ALTER DATABASE REGISTER LOGFILE'/ home/oracle/archive_gap/orcl_53415_710350416.log';Database altered.

Check again

SQL > select * from vault archiveGap; this is the end of the article on "how to solve the problem of Dataguard log transmission status monitoring in Oracle". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.