1.Standby database process status: You can run following query on standby database to see what MRP and RFS processes are doing, which block of which archivelog sequences are being shipped or being applied.
SQL> select process, status, thread#, sequence#, block#, blocks from v$managed_standby ;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH CLOSING1 301 75776 1432
ARCH CLOSING1 299 77824 1825
ARCH CONNECTED0 0 0 0
ARCH CLOSING1 300 75776 1422
RFS IDLE0 0 0 0
RFS IDLE0 0 0 0
RFS IDLE1 302 72377 1
MRP0 WAIT_FOR_LOG1 302 0 0
8 rows selected.
2.Last applied log: Run this query on the standby database to see the last applied archivelog sequence number for each thread.
SQL> SELECT thread#, max(SEQUENCE#) FROM V$ARCHIVED_LOG where APPLIED='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
---------- --------------
1 301
3.Archivelog difference: Run this on primary database. (not for real time apply)
SQL> ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YYYY HH24:MI:SS';
Session altered.
SQL> SELECT a.thread#, b. last_seq, a.applied_seq, a. last_app_timestamp, b.last_seq-a.applied_seq ARC_DIFF FROM (SELECT thread#, MAX(sequence#) applied_seq, MAX(next_time) last_app_timestamp FROM gv$archived_log WHERE applied = 'YES' GROUP BY thread#) a, (SELECT thread#, MAX (sequence#) last_seq FROM gv$archived_log GROUP BY thread#) b WHERE a.thread# = b.thread#;
THREAD# LAST_SEQ APPLIED_SEQ LAST_APP_TIMESTAMP ARC_DIFF
---------- ---------- ----------- -------------------- ----------
1 301 301 08-OCT-2015 01:06:460
4.Apply/transport lags: v$dataguard_stats view will show the general synchronization status of standby database.
SQL> select * from v$dataguard_stats;
NAME VALUE UNIT TIME_COMPUTED DATUM_TIME
------------------------- -------------------- ------------------------------ ------------------------------ ------------------------------
transport lag +00 00:00:00 day(2) to second(0) interval 10/08/2015 09:21:40 10/08/2015 09:21:39
apply lag +00 08:14:59 day(2) to second(0) interval 10/08/2015 09:21:40 10/08/2015 09:21:39
apply finish time +00 00:00:02.091 day(2) to second(3) interval 10/08/2015 09:21:40
estimated startup time 19 second 10/08/2015 09:21:40
5.
SQL> select * from v$recovery_progress;
START_TIM TYPE ITEM UNITSSOFARTOTAL TIMESTAMP COMMENTS
--------- ------------------------------ ------------------------- --------------- ---------- ------- --------- --------------------
23-SEP-15 Media Recovery Log Files Files 229 0
23-SEP-15 Media Recovery Active Apply Rate KB/sec16045 0
23-SEP-15 Media Recovery Average Apply Rate KB/sec 6 0
23-SEP-15 Media Recovery Maximum Apply Rate KB/sec17761 0
23-SEP-15 Media Recovery Redo Applied Megabytes 7891 0
23-SEP-15 Media Recovery Last Applied Redo SCN+Time 0 0 08-OCT-15 SCN: 3957818
23-SEP-15 Media Recovery Active Time Seconds 871 0
23-SEP-15 Media Recovery Apply Time per Log Seconds 3 0
23-SEP-15 Media Recovery Checkpoint Time per Log Seconds 0 0
23-SEP-15 Media Recovery Elapsed Time Seconds 1248075 0
23-SEP-15 Media Recovery Standby Apply Lag Seconds14784 0
11 rows selected.
亿速云「云服务器」,即开即用、新一代英特尔至强铂金CPU、三副本存储NVMe SSD云盘,价格低至29元/月。点击查看>>
免责声明:本站发布的内容(图片、视频和文字)以原创、转载和分享为主,文章观点不代表本网站立场,如果涉及侵权请联系站长邮箱:is@yisu.com进行举报,并提供相关证据,一经查实,将立刻删除涉嫌侵权内容。