• 博客园logo
  • 会员
  • 众包
  • 新闻
  • 博问
  • 闪存
  • 赞助商
  • HarmonyOS
  • Chat2DB
    • 搜索
      所有博客
    • 搜索
      当前博客
  • 写随笔 我的博客 短消息 简洁模式
    用户头像
    我的博客 我的园子 账号设置 会员中心 简洁模式 ... 退出登录
    注册 登录

Frank_20160505

  • 博客园
  • 联系
  • 订阅
  • 管理

公告

View Post

[Oracle][DATAGUARD] 关于确认PHYSICAL STANDBY的同期状况的方法

补上简单的确认PHYSICAL STANDBY的同期状况的方法:

ODM TEST CASE
===================
Name = TC#1010_3

####Primary####

SQL> set line 200
col name for a100SQL>
SQL> select instance_name,status from v$instance;

INSTANCE_NAME                                    STATUS
------------------------------------------------ ------------------------------------
orcl                                             OPEN

SQL> select database_role from v$database;

DATABASE_ROLE
------------------------------------------------
PRIMARY ★Primary

SQL> select sequence#-1 from v$log where status='CURRENT';

SEQUENCE#-1
-----------
       61 ★on Primary, Latest ONLINE Redo number is 61


####Standby####


SQL> set line 200
col name for a100SQL>
SQL> select instance_name,status from v$instance;

INSTANCE_NAME                                    STATUS
------------------------------------------------ ------------------------------------
orcls                                            OPEN

SQL> select database_role from v$database;

DATABASE_ROLE
------------------------------------------------
PHYSICAL STANDBY ★PHYSICAL STANDBY

SQL> select sequence#, name, applied from v$archived_log where resetlogs_change# = (select resetlogs_change# from v$database) order by sequence#;

SEQUENCE# NAME                                                                                                 APPLIED
---------- ---------------------------------------------------------------------------------------------------- ---------------------------
      54                                                                                                      YES
      55 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_01_09/o1_mf_1_55_d768d472_.arc              YES
      56 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_01_09/o1_mf_1_56_d768dvdr_.arc              IN-MEMORY ★
      57 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_57_dsb0ljby_.arc              NO
      58 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_58_dsb0lgkq_.arc              NO
      59 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_59_dsb0lgk1_.arc              NO
      60 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_60_dsb0ljc1_.arc              NO
      61 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_61_dsb0mg3z_.arc              NO ★on Standby,no Redo transportation rag , but there is REDO application rag.

8行が選択されました。

SQL> recover managed standby database using current logfile disconnect; ★start REDO application
メディア・リカバリが完了しました。
SQL> select PROCESS,PID,STATUS,THREAD#,SEQUENCE# from V$MANAGED_STANDBY where PROCESS='MRP0'; ★MRP process is on (if there is no record here , it means MRP is not on )

PROCESS                            PID STATUS                                  THREAD#  SEQUENCE#
--------------------------- ---------- ------------------------------------ ---------- ----------
MRP0                              2898 APPLYING_LOG                                  1         62

SQL> select sequence#, name, applied from v$archived_log where resetlogs_change# = (select resetlogs_change# from v$database) order by sequence#;

SEQUENCE# NAME                                                                                                 APPLIED
---------- ---------------------------------------------------------------------------------------------------- ---------------------------
      54                                                                                                      YES
      55 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_01_09/o1_mf_1_55_d768d472_.arc              YES
      56 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_01_09/o1_mf_1_56_d768dvdr_.arc              YES
      57 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_57_dsb0ljby_.arc              YES
      58 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_58_dsb0lgkq_.arc              YES
      59 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_59_dsb0lgk1_.arc              YES
      60 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_60_dsb0ljc1_.arc              YES
      61 /u01/app/oracle/fast_recovery_area/ORCLS/archivelog/2017_08_17/o1_mf_1_61_dsb0mg3z_.arc              IN-MEMORY ★If there is no REDO application rag and Redo transportation rag on Standby, the "APPLIED" column of Latest SEQUENCE should be "IN-MEMORY"(expected behavior)

8行が選択されました。

posted on 2017-10-10 19:07  Frank_20160505  阅读(217)  评论(0)    收藏  举报

刷新页面返回顶部
 
博客园  ©  2004-2025
浙公网安备 33010602011771号 浙ICP备2021040463号-3