oracle dataguard主备库切换后出现：FAL[server]: Fail to queue the whole FAL gap
主库与备库发生切换后，出现以下信息。ARC9: Standby redo logfile selected for thread 1 sequence 59 for destination LOG_ARCHIVE_DEST_Fri May 18 14:21:56 2012
FAL[server]: Fail to queue the whole FAL gap
3gDW0?dq9664900 GAP - thread 1 sequence 58- DBID 2847860684 branch 729500050经查询，以上问题属于oracle bug，这个bug只存在于Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.3 - Release: 10.1 to 10.2

解决方法如下：
SolutionThis 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.

官方原文如下：
FAL Message In Alert.log When No Gap In Standby [ID 601841.1]
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***
SymptomsWhen 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:

[font=NSimsun]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:
[font=NSimsun]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

[font=NSimsun]SQL> select * from v$archive_gap;
no rows selected

CauseBug 5526409 - FAL gaps reported at standby for log not yet written at primary
SolutionThis 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.