How does Oracle 11g RAC query physical standby delay

This article will explain in detail how to query the delay of the physical repository in Oracle 11g RAC. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

The V$DATAGUARD_STATS view provides information about how far behind the redo transfer and redo application processes are.

Execute the following SQL script in the physical repository:

COL NAME FOR A13

COL VALUE FOR A20

COL UNIT FOR A30

SET LINES 122

SELECT NAME,VALUE,UNIT,TIME_COMPUTED

FROM V$DATAGUARD_STATS

WHERE NAME IN ('transport lag','apply lag')

SQL > COL NAME FOR A13

SQL > COL VALUE FOR A20

SQL > COL UNIT FOR A30

SQL > SET LINES 122

SQL > SELECT NAME,VALUE,UNIT,TIME_COMPUTED

2 FROM V$DATAGUARD_STATS

3 WHERE NAME IN ('transport lag','apply lag')

NAME VALUE UNIT TIME_COMPUTED

-

Transport lag + 00 00:00:00 day (2) to second (0) interval 10 max 31 max 14:42:31

Apply lag + 00 00:00:01 day (2) to second (0) interval 10 max 31 max 14:42:31

The 00:00:00 transfer lag value of transport lag indicates that the redo data transfer from the primary database to the physical standby database is 0 seconds behind.

If there is a disaster on the primary database and you lose the primary site, you have to tolerate the loss of 0 seconds of data, no data loss, or if you want to perform a switch, you need to wait 0 seconds without waiting.

Note that the application lag value of 00:00:01 indicates that the application lagged by 1 second. The lag value reflects the DELAY characteristic of 30 minutes in the ARCHIVE_LOG_DEST_n parameter.

This is the end of the article on "how to query the delay of Oracle 11g RAC". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.