驗證物理備庫是否執行正常
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種方法
- 驗證是否成功
- Oracle:Failover 到物理備庫OracleAI
- 10 管理物理和快照備庫
- 驗證資料是否存在
- Spark原理-物理執行圖Spark
- win10必備執行庫怎麼安裝_win10必備執行庫有哪些Win10
- 正常執行時間監控
- 使用Moya庫,進行https證書校驗HTTP
- rman如何在備庫執行一致性備份
- BAT批處理判斷服務是否正常執行(批處理命令綜合應用)BAT
- python使用多執行緒備份資料庫Python執行緒資料庫
- 使用Data Guard Broker進行Data Guard物理備用庫配置(Oracle 19c)Oracle
- 驗證物件是否為空的工具類物件
- python怎麼驗證檔案是否存在Python
- oracle驗證設定的event是否生效:Oracle
- hystrix執行緒池隔離的原理與驗證執行緒
- yii2 日誌自動傳送到釘釘 實時監控服務是否執行正常
- 11. shell多執行緒備份資料庫執行緒資料庫
- 執行緒數,512是否合理?執行緒
- 中國身份證號驗證庫
- 1.6.5.1. 準備使用密碼檔案進行身份驗證密碼
- jQuery Validate驗證確認密碼是否相同jQuery密碼
- 驗證輸入的字串是否為合法日期字串
- 保證執行緒在主執行緒執行執行緒
- 【DATAGUARD】Oracle Dataguard物理備庫切換最佳實踐(sqlplus)OracleSQL
- DM聯機執行SQL語句進行資料庫備份SQL資料庫
- 小說軟體原始碼的快取設計,保證服務的正常執行原始碼快取
- 藉助Windows自帶的ODBC工具驗證資料庫連線是否通暢Windows資料庫
- oracle 增量備份恢復驗證Oracle
- 執行 PHP artisan queue:work 一直 processing 非正常執行處理PHP
- Shell多執行緒備份資料庫的指令碼執行緒資料庫指令碼
- 南大通用GBase資料庫為城軌交通正常執行保駕護航資料庫
- 利用JS驗證使用者名稱是否合法JS
- Oracle 12c 使用RMAN搭建物理備庫(RAC to RAC)Oracle
- 如何檢視 Apache 模組是否正常Apache
- 如何檢查是否物理伺服器?伺服器
- 【RMAN】在備庫執行rman備份時報錯RMAN-06820 ORA-17629
- Oracle檢視歸檔是否被備庫應用Oracle