DG模拟备库故障以及修复后相关日志分析处理

备库模拟故障 进行shutdown，主库进行大量事务。主库日志 ：
  Current log# 2 seq# 56 mem# 0: /u01/app/oracle/oradata/orcl/redo02.log
Fri Jun 22 15:31:04 2018
Archived Log entry 93 added for thread 1 sequence 55 ID 0x59d5dd20 dest 1:
Fri Jun 22 15:31:27 2018
Thread 1 cannot allocate new log, sequence 57
Checkpoint not complete
  Current log# 2 seq# 56 mem# 0: /u01/app/oracle/oradata/orcl/redo02.log
Thread 1 advanced to log sequence 57 (LGWR switch)
  Current log# 3 seq# 57 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log
Fri Jun 22 15:31:31 2018
Archived Log entry 94 added for thread 1 sequence 56 ID 0x59d5dd20 dest 1:
Thread 1 cannot allocate new log, sequence 58
Checkpoint not complete
  Current log# 3 seq# 57 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log
Thread 1 advanced to log sequence 58 (LGWR switch)
  Current log# 1 seq# 58 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log
Fri Jun 22 15:31:36 2018
Archived Log entry 95 added for thread 1 sequence 57 ID 0x59d5dd20 dest 1:
Thread 1 cannot allocate new log, sequence 59
Checkpoint not complete
  Current log# 1 seq# 58 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log
Fri Jun 22 15:31:40 2018
Thread 1 advanced to log sequence 59 (LGWR switch)
  Current log# 2 seq# 59 mem# 0: /u01/app/oracle/oradata/orcl/redo02.log
Fri Jun 22 15:31:41 2018
Archived Log entry 96 added for thread 1 sequence 58 ID 0x59d5dd20 dest 1:
Thread 1 cannot allocate new log, sequence 60
Checkpoint not complete
  Current log# 2 seq# 59 mem# 0: /u01/app/oracle/oradata/orcl/redo02.log
Thread 1 advanced to log sequence 60 (LGWR switch)
  Current log# 3 seq# 60 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log
Fri Jun 22 15:31:47 2018
Archived Log entry 97 added for thread 1 sequence 59 ID 0x59d5dd20 dest 1:
Fri Jun 22 15:33:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:34:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.-----arch 开始ping备库
Fri Jun 22 15:33:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:34:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:35:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:36:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:37:10 2018
Error 1034 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 1034.
Fri Jun 22 15:38:10 2018
PING[ARC2]: Heartbeat failed to connect to standby 'orcldg'. Error is 16058.
Fri Jun 22 15:39:10 2018









备用数据库修复完成启动 ，
1 主库切换日志 ，启动LNS传输新的orl
2 arch ping开始处理间隔日志。


ARC0: Standby redo logfile selected for thread 1 sequence 51 for destination LOG_ARCHIVE_DEST_2 --处理arch间隔
Fri Jun 22 15:39:13 2018
LGWR: Standby redo logfile selected for thread 1 sequence 61 for destination LOG_ARCHIVE_DEST_2  --切日志 
Thread 1 advanced to log sequence 61 (LGWR switch)
  Current log# 1 seq# 61 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log
Fri Jun 22 15:39:13 2018
Archived Log entry 100 added for thread 1 sequence 60 ID 0x59d5dd20 dest 1:





备库操作 ：
启动MRP自动恢复吧




Attempt to start background Managed Standby Recovery process (orcl)
Fri Jun 22 15:44:07 2018
MRP0 started with pid=29, OS id=4100 
MRP0: Background Managed Standby Recovery process started (orcl)
 started logmerger process
Fri Jun 22 15:44:12 2018
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /DBBackup/Archive/1_51_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_52_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_53_979402914.dbf
Completed: alter database recover managed standby database using current logfile disconnect from session 
Media Recovery Log /DBBackup/Archive/1_54_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_55_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_56_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_57_979402914.dbf
Fri Jun 22 15:44:23 2018
Media Recovery Log /DBBackup/Archive/1_58_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_59_979402914.dbf
Media Recovery Log /DBBackup/Archive/1_60_979402914.dbf
Media Recovery Waiting for thread 1 sequence 61 (in transit)
Recovery of Online Redo Log: Thread 1 Group 4 Seq 61 Reading mem 0
  Mem# 0: /u01/app/oracle/oradata/orcl/sbredo04.log




SQL> alter database recover managed standby database CANCEL;


Database altered.


SQL> ALTER DATABASE OPEN READ ONLY;


Database altered.


SQL> alter database recover managed standby database using current logfile disconnect from session ;


Database altered.


SQL> SELECT OPEN_MODE FROM V$DATABASE;
SELECT OPEN—DE FROM V$DATABASE
       *
ERROR at line 1:
ORA-00904: "OPEN—DE": invalid identifier




SQL> select open_mode from v$database;


OPEN_MODE
--------------------
READ ONLY WITH APPLY


SQL> 

##################测试是否同步小技巧####################

1 在主库模拟产生大量redo 的事务，查看备库日志应用情况以及刷新情况。