Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

[DataGuard] Oracle DataGuard log transfer status monitoring

2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

Oracle 11g DataGuard log transfer status monitoring

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.

[experimental environment] operating system: Red Hat Enterprise Linux Server release 5.4

Database: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0

Main library Primary database: green

Physical repository Physical standby database: yellow

[experimental process] 1. Master and standby 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 v$log

Select archived_thread#,archived_seq#,applied_thread#,applied_seq# from v$archive_dest_status

4. Prepare the database to view the archived redo

Elect 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

[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.

LV Xinghao

2014.8.24

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report