Data Guard出现gap sequence

Data Guard出现gap sequence

修复 一、问题描述 今天下午客户那边断电,导致了其中一个备库数据库起不来,报了下面的错误 SQL Media Recovery Waiting for thread 1 sequence 12364 Fetching gap sequence in thread 1, gap sequence 12364-12364 Wed Jan 17 15:20:57 2018 FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 12364-12364 DBID 3677888493 branch 946469421 FAL[client]: All defined FAL servers have been attempted. ------------------------------------------------------------ Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that's sufficiently large enough to maintain adequate log switch information to resolve archivelog gaps.

二、修复操作

1.查询备库中的GAP 出现时的最小SEQ SQL SQL> select FIRST_CHANGE# from v$archived_log where SEQUENCE# =12364;

FIRST_CHANGE#

------------- 139323967

--在出现意外datafile header scn不一致的时候,需要根据提示归档日志,找出最小scn

2.确定主库是否添加数据文件

SQL SQL> select file#,name from v$datafile where creation_change#> =139323967;

no rows selected

确定主库在这个scn之后是否有添加数据文件,如果添加文件,需要手工在备库添加

3.备库停止日志应用

SQL SQL> alter database recover managed standby database cancel; Database altered.

4.主库增量备份并传输到备库上 主库进行增量备份

SQL RMAN> backup incremental from scn 139323967 database format '/backup/cebpm/fullbackup/cebpm_%U' tag 'cebpm';

上传到备库 SQL cebpm:/backup/cebpm/fullbackup@cebpm>

scp cebpm_* 132.237.0.206:/backup/cebpm/rman

5.备库上进行恢复 将备库启动到mount 状态,然后执行下面的语句 SQL cebpmxc:/data/ORAdata/cebpmxc/archivelog@xiechuang>rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jan 17 16:21:54 2018 Copyright (c) 1982, 2011, oracle and/or its affiliates. All rights reserved. connected to target database: CEBPM (DBID=3677888493)

RMAN> catalog start with '/backup/cebpm/rman';

using target database control file instead of recovery catalog searching for all files that match the pattern /backup/cebpm/rman List of Files Unknown to the Database ===================================== File Name: /backup/cebpm/rman/cebpm_p1sotn4f_1_1 File Name: /backup/cebpm/rman/cebpm_otsotn28_1_1 File Name: /backup/cebpm/rman/cebpm_ousotn31_1_1 File Name: /backup/cebpm/rman/cebpm_ovsotn3g_1_1 File Name: /backup/cebpm/rman/cebpm_orsotn0l_1_1 File Name: /backup/cebpm/rman/cebpm_ossotn1p_1_1 File Name: /backup/cebpm/rman/cebpm_p0sotn40_1_1 File Name: /backup/cebpm/rman/cebpm_opsotlob_1_1 File Name: /backup/cebpm/rman/cebpm_p2sotn4u_1_1 File Name: /backup/cebpm/rman/cebpm_oqsotmg8_1_1 Do you really want to catalog the above files (enter YES or NO)? yes cataloging files... cataloging done List of Cataloged Files ======================= File Name: /backup/cebpm/rman/cebpm_p1sotn4f_1_1 File Name: /backup/cebpm/rman/cebpm_otsotn28_1_1 File Name: /backup/cebpm/rman/cebpm_ousotn31_1_1 File Name: /backup/cebpm/rman/cebpm_ovsotn3g_1_1 File Name: /backup/cebpm/rman/cebpm_orsotn0l_1_1 File Name: /backup/cebpm/rman/cebpm_ossotn1p_1_1 File Name: /backup/cebpm/rman/cebpm_p0sotn40_1_1 File Name: /backup/cebpm/rman/cebpm_opsotlob_1_1 File Name: /backup/cebpm/rman/cebpm_p2sotn4u_1_1 File Name: /backup/cebpm/rman/cebpm_oqsotmg8_1_1 RMAN> recover database noredo; Starting recover at 2018/01/17 16:26:05 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=226 device type=DISK channel ORA_DISK_1: starting incremental datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set destination for restore of datafile

RMAN> alter database mount;

database mounted released channel:

8.清空备库日志组

SQL sql> alter database clear logfile group

1; 注:如果采用了standby log模式,不需要清空,如果清空会出现

SQL sql> alter database clear logfile group 1;

alter database clear logfile group 1 * error at line 1: ora-19527: physical standby redo log must be renamed ora-00312: online log 1 thread 1: '/data/oradata/cebpmxc/redo/redo01.l

说明:如果没有采用standby log模式,有几组需要清空几组

9.备库重设Flashback

SQL sql> alter database flashback off;

10.备库重新接收并应用日志

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

Database altered

三、验证 1.sql 中操作 在主库中执行alter system switch logfile;

分别主备库中执行select max(sequence#) from v$archived_log;

如果一致标示修复成功

2.通过alert文件 主库:

SQL Wed Jan 17 17:34:08 2018 Thread 1 advanced to log sequence 14197 (LGWR switch) Current log# 4 seq# 14197 mem# 0: /data1/oradata/cebpm/redo/redo04.log Current log# 4 seq# 14197 mem# 1: /data2/oradata/cebpm/redo/redo04.rdo Archived Log entry 40323 added for thread 1 sequence 14196 ID 0xdb3769ed dest 1: Wed Jan 17 17:34:09 2018 LNS: Standby redo logfile selected for thread 1 sequence 14197 for destination LOG_ARCHIVE_DEST_2 LNS: Standby redo logfile selected for thread 1 sequence 14197 for destination LOG_ARCHIVE_DEST_3 备库: Media Recovery Waiting for thread 1 sequence 14196 (in transit) Recovery of Online Redo Log: Thread 1 Group 12 Seq 14196 Reading mem 0   Mem# 0: /data/oradata/cebpmxc/redo/redo12_stb01.log RFS[1]: Selected log 11 for thread 1 sequence 14197 dbid -617078803 branch 946469421 Wed Jan 17 17:38:52 2018 Archived Log entry 13 added for thread 1 sequence 14196 ID 0xdb3769ed dest 1: Media Recovery Waiting for thread 1 sequence 14197 (in transit) Recovery of Online Redo Log: Thread 1 Group 11 Seq 14197 Reading mem 0   Mem# 0: /data/oradata/cebpmxc/redo/redo11_stb01.log 至此DG恢复完成,记住最后还有一步就是把flashback打开。本文来自:雨花石,原地址:https://www.yuhuashi.infohttps://www.yuhuashi.info/post/42.html

猜你喜欢

转载自blog.csdn.net/m18994118189/article/details/81901369