ITPub博客

首页 > Linux操作系统 > Linux操作系统 > FAL Message In Alert.log When No Gap In Standby

FAL Message In Alert.log When No Gap In Standby

原创 Linux操作系统 作者:paulyibinyi 时间:2011-07-26 16:33:18 0 删除 编辑

In this Document
  Symptoms
  Cause
  Solution
  References


Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.3 - Release: 10.1 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 25-MAR-2011***

Symptoms

When using ARCH transport, gaps could be flagged in the alert log even though the single log gap was for a log that had not been written at the primary yet.

alert.log on primary shows:

FAL[server]: Fail to queue the whole FAL gap
GAP - thread 1 sequence 63962-63962
DBID 1243807152 branch 631898097

or alert.log on standby shows:

Fetching gap sequence in thread 1, gap sequence 63962-63962
Thu Jan 24 14:36:30 2008
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 63962-63962
DBID 2004523329 branch 594300676
FAL[client]: All defined FAL servers have been attempted.


v$archive_gap returns no rows

SQL> select * from v$archive_gap;
no rows selected

Cause

Bug 5526409 - FAL gaps reported at standby for log not yet written at primary

Solution

This is a known Bug 5526409 which is fixed in 10.2.0.4 and 11.1.

To solve the issue, please upgrade to the newest patchset since Bug 5526409 is fixed in 10.2.0.4.

Their is no impact of these messages on the database. You can safely ignore these messages.

Furthermore there are One-off Patch for Bug 5526409 on top of 10.2.0.3  available for some platforms. Please check  Patches & Updates within My Oracle Support MOS.

References

BUG:5526409 - FAL[CLIENT]: FAILED TO REQUEST GAP SEQUENCE BUT NO GAPS FOUND
PATCH:5526409 - FAL[CLIENT]: FAILED TO REQUEST GAP SEQUENCE BUT NO GAPS FOUND

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/7199859/viewspace-703151/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
学习数据库

注册时间:2007-12-11

  • 博文量
    902
  • 访问量
    6597747