风哥教程

培训 . 交流 . 分享
Make progress together!

oracle dataguard主备库切换后出现FAL[server]: Fail to queue the whole FAL ...

[复制链接]
内容发布:风哥| 发布时间:2013-12-24 14:50:23
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:


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


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.




上一篇:在Oracle DataGuard环境中使用Broker-角色转换Switchover
下一篇:oracle权限管理Revoking DBA Roles Revokes UNLIMITED TABLESPACE from the user
专业提供Oracle/MySQL/NoSQL/Linux数据库培训与技术支持服务,QQ号:113257174
关注风哥教程微信公众号itpux_com  ,了解本站最新技术资料的分享.

欢迎加QQ群,提供超多高质量Oracle/Unix/Linux技术文档与视频教程的下载。

Oracle/MySQL/Linux群4-5:189070296  150201289  
Oracle/MySQL/Linux群6-8:244609803   522261684   522651731
备注:请勿重复加群,另请注明 from itpux
回复

使用道具 举报

1框架
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

热门文章教程

  • Oracle19c数据库发布与下载地址
  • 风哥Oracle数据库巡检工具V1.0(附2.6网页
  • Oracle Database 12c 数据库100个新特性与
  • Oracle 12cR2 九大新功能全面曝光_详解云数
  • 实战PHP与MySQL权威指南PDF电子书下载
  • 大数据技术与应用入门培训教程(电子版下载
快速回复 返回顶部 返回列表