驗證物理備庫是否執行正常
Verify the Physical Standby Database Is Performing Properly
Once you create the physical standby database and set up redo transport services, you may want to verify database modifications are being successfully transmitted from
the primary database to the standby database.
To see that redo is being received on the standby database, you should first identify the existing archived redo log files on the standby database, force a log
switch and archive a few online redo log files on the primary database, and then check the standby database again. The following steps show how to perform. these tasks.
Step 1 Identify the existing archived redo log files.
On the standby database, query the V$ARCHIVED_LOG view to identify existing files in the archived redo log. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
---------- ------------------ ------------------
8 11-JUL-07 17:50:45 11-JUL-07 17:50:53
9 11-JUL-07 17:50:53 11-JUL-07 17:50:58
10 11-JUL-07 17:50:58 11-JUL-07 17:51:03
3 rows selected.
Step 2 Force a log switch to archive the current online redo log file.
On the primary database, issue the ALTER SYSTEM SWITCH LOGFILE statement to force a log switch and archive the current online redo log file group:
SQL> ALTER SYSTEM SWITCH LOGFILE;
Step 3 Verify the new redo data was archived on the standby database.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo data was received and archived on the standby database:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
---------- ------------------ ------------------
8 11-JUL-07 17:50:45 11-JUL-07 17:50:53
9 11-JUL-07 17:50:53 11-JUL-07 17:50:58
10 11-JUL-07 17:50:58 11-JUL-07 17:51:03
11 11-JUL-07 17:51:03 11-JUL-07 18:34:11
4 rows selected.
The archived redo log files are now available to be applied to the physical standby database.
Step 4 Verify that received redo has been applied.
On the standby database, query the V$ARCHIVED_LOG view to verify that received redo has been applied:
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# APP
--------- ---
8 YES
9 YES
10 YES
11 IN-MEMORY
4 rows selected.
Once you create the physical standby database and set up redo transport services, you may want to verify database modifications are being successfully transmitted from
the primary database to the standby database.
To see that redo is being received on the standby database, you should first identify the existing archived redo log files on the standby database, force a log
switch and archive a few online redo log files on the primary database, and then check the standby database again. The following steps show how to perform. these tasks.
Step 1 Identify the existing archived redo log files.
On the standby database, query the V$ARCHIVED_LOG view to identify existing files in the archived redo log. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
---------- ------------------ ------------------
8 11-JUL-07 17:50:45 11-JUL-07 17:50:53
9 11-JUL-07 17:50:53 11-JUL-07 17:50:58
10 11-JUL-07 17:50:58 11-JUL-07 17:51:03
3 rows selected.
Step 2 Force a log switch to archive the current online redo log file.
On the primary database, issue the ALTER SYSTEM SWITCH LOGFILE statement to force a log switch and archive the current online redo log file group:
SQL> ALTER SYSTEM SWITCH LOGFILE;
Step 3 Verify the new redo data was archived on the standby database.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo data was received and archived on the standby database:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
---------- ------------------ ------------------
8 11-JUL-07 17:50:45 11-JUL-07 17:50:53
9 11-JUL-07 17:50:53 11-JUL-07 17:50:58
10 11-JUL-07 17:50:58 11-JUL-07 17:51:03
11 11-JUL-07 17:51:03 11-JUL-07 18:34:11
4 rows selected.
The archived redo log files are now available to be applied to the physical standby database.
Step 4 Verify that received redo has been applied.
On the standby database, query the V$ARCHIVED_LOG view to verify that received redo has been applied:
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# APP
--------- ---
8 YES
9 YES
10 YES
11 IN-MEMORY
4 rows selected.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26194851/viewspace-751571/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- dataguard驗證是否正常同步的2種方法
- 物理備庫failover實驗AI
- rac與邏輯備庫不能自動建表空間,物理備庫正常
- Oracle 12c Data guard 物理主備庫正常切換(switchover)流程Oracle
- Oracle 11g Data guard 物理主備庫正常切換(switchover)流程Oracle
- 執行時驗證概述
- 驗證是否成功
- 物理備庫互轉快照備庫
- 配置物理備庫+邏輯備庫
- 搭建物理備庫
- 2 Day DBA-管理方案物件-執行備份和恢復-備份資料庫-驗證選擇的備份物件資料庫
- 2 Day DBA-管理方案物件-執行備份和恢復-備份資料庫-為還原操作驗證備份物件資料庫
- 使用 xtrabackup 進行MySQL資料庫物理備份MySql資料庫
- 驗證資料是否存在
- 2 Day DBA-管理方案物件-執行備份和恢復-備份資料庫-驗證備份並測試你的備份策略物件資料庫
- 10 管理物理和快照備庫
- Oracle:Failover 到物理備庫OracleAI
- 物理備庫的搭建過程
- RMAN DUPLICATE建立DataGuard物理備庫
- 物理備用資料庫(二)資料庫
- 物理備用資料庫(一)資料庫
- Spark原理-物理執行圖Spark
- 資料庫正常執行,突然變慢的解決思路資料庫
- dataguard-建立物理備庫全程解析
- 重建物理備庫案例兩則
- 物理備庫無法接受archivelogHive
- SOS?求教執行CMP之create,能正常執行,但資料庫中無資料資料庫
- 【DG】怎麼使用Data Pump備份物理備庫
- 正常執行時間監控
- Server正常執行整1年。Server
- win10必備執行庫怎麼安裝_win10必備執行庫有哪些Win10
- test是否被執行?
- 在物理備庫上部署閃回資料庫資料庫
- 單節點主庫、邏輯備庫升級為RAC、物理備庫、邏輯備庫(1)
- 單節點主庫、邏輯備庫升級為RAC、物理備庫、邏輯備庫(2)
- 單節點主庫、邏輯備庫升級為RAC、物理備庫、邏輯備庫(3)
- 單節點主庫、邏輯備庫升級為RAC、物理備庫、邏輯備庫(4)
- 單節點主庫、邏輯備庫升級為RAC、物理備庫、邏輯備庫(5)