oracle wait for,Oracle Dataguard WAIT_FOR_GAP error

Hi,

I have a Oracle Dataguard 10.2 running on Windows and found a WAIT_FOR_GAP error on the standby server.

--> alert log of standby

Sun Jan 30 20:00:04 2011

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

MRP0 started with pid=18, OS id=2452

Managed Standby Recovery not using Real Time Apply

parallel recovery started with 3 processes

Sun Jan 30 20:00:13 2011

Waiting for all non-current ORLs to be archived...

Clearing online redo logfile 10 E:\ORACLE\A30\ORIGLOGA\LOG_G10_M1.DBF

Clearing online log 10 of thread 1 sequence number 17848

Sun Jan 30 20:00:13 2011

Errors in file z:\oracle\a30\saptrace\background\a30_mrp0_2452.trc:

ORA-19527: physical standby redo log must be renamed

ORA-00312: online log 10 thread 1: 'E:\ORACLE\A30\ORIGLOGA\LOG_G10_M1.DBF'

Clearing online redo logfile 10 complete

Media Recovery Log L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17856_0681431456.001

Sun Jan 30 20:00:13 2011

Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

Sun Jan 30 20:00:33 2011

Media Recovery Waiting for thread 1 sequence 17857

Sun Jan 30 20:51:19 2011

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

RFS[636]: Assigned to RFS process 4976

RFS[636]: Identified database type as 'physical standby'

Primary database is in MAXIMUM PERFORMANCE mode

Primary database is in MAXIMUM PERFORMANCE mode

Sun Jan 30 20:51:20 2011

Fetching gap sequence in thread 1, gap sequence 17857-17863

Sun Jan 30 20:51:20 2011

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

RFS[637]: Assigned to RFS process 4012

RFS[637]: Identified database type as 'physical standby'

Sun Jan 30 20:52:20 2011

RFS[637]: Archived Log: 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17864_0681431456.001'

Sun Jan 30 20:56:34 2011

FAL[client]: Failed to request gap sequence

GAP - thread 1 sequence 17857-17863

DBID 3371425568 branch 681431456

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 is sufficiently large

enough to maintain adequate log switch information to resolve

archivelog gaps.

-------------------------------------------------------------

Sun Jan 30 22:00:44 2011

RFS[636]: Archived Log: 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17865_0681431456.001'

Primary database is in MAXIMUM PERFORMANCE mode

SQL> select process,sequence#,status from v$managed_standby;

PROCESS SEQUENCE# STATUS

--------- ---------- ------------

ARCH 0 CONNECTED

ARCH 0 CONNECTED

MRP0 17857 WAIT_FOR_GAP

RFS 0 IDLE

RFS 0 IDLE

RFS 0 IDLE

SQL> select * from v$archive_gap;

THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#

---------- ------------- --------------

1 17857 17863

SQL> select sequence#,applied from v$archived_log order by sequence#;

SEQUENCE# APP

---------- ---

17855 YES

17856 YES

17864 NO

17865 NO

17866 NO

17867 NO

17868 NO

17869 NO

17870 NO

17871 NO

17872 NO

SEQUENCE# APP

---------- ---

17873 NO

17874 NO

17875 NO

17876 NO

17877 NO

17878 NO

17879 NO

17889 NO

17890 NO

17891 NO

17892 NO

...............

SEQUENCE# APP

---------- ---

18067 NO

18068 NO

18069 NO

18070 NO

18071 NO

18072 NO

4032 rows selected.

--> alert log of primary

Sun Jan 30 20:00:03 2011

Incremental checkpoint up to RBA [0x45c8.1f6c6.0], current log tail at RBA [0x45c8.1f7f5.0]

Sun Jan 30 20:05:04 2011

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;

Sun Jan 30 20:30:11 2011

Incremental checkpoint up to RBA [0x45c8.201e2.0], current log tail at RBA [0x45c8.20215.0]

Sun Jan 30 20:51:12 2011

Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED

******************************************************************

LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

******************************************************************

LNSb started with pid=50, OS id=1792

Sun Jan 30 20:51:19 2011

Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION

Beginning log switch checkpoint up to RBA [0x45c9.2.10], SCN: 276988485

Sun Jan 30 20:51:20 2011

Thread 1 advanced to log sequence 17865 (LGWR switch)

Current log# 17 seq# 17865 mem# 0: F:\ORACLE\A30\ORIGLOGB\LOG_G17_M1.DBF

Current log# 17 seq# 17865 mem# 1: E:\ORACLE\A30\MIRRLOGB\LOG_G17_M2.DBF

Sun Jan 30 20:51:20 2011

ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2

Sun Jan 30 20:51:25 2011

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Redo Shipping Client Connected as PUBLIC

-- Connected User is Valid

Sun Jan 30 20:56:35 2011

Completed checkpoint up to RBA [0x45c9.2.10], SCN: 276988485

Sun Jan 30 21:00:24 2011

Incremental checkpoint up to RBA [0x45c9.fac0.0], current log tail at RBA [0x45c9.10256.0]

Sun Jan 30 21:30:31 2011

Incremental checkpoint up to RBA [0x45c9.104c1.0], current log tail at RBA [0x45c9.104f4.0]

Sun Jan 30 22:00:36 2011

Incremental checkpoint up to RBA [0x45c9.2c3d7.0], current log tail at RBA [0x45c9.2c94e.0]

I think the error is due to LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED as seen in the primary server.

I have placed the missing logs 17857-17863 in archive directory of primary so that it can be shipped over to standby

but error persists.

Kindly advise what should be done to resolve the WAIT_FOR_GAP error.

Thanks in advance!

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值