当前位置: 首页 > ORACLE > 正文

ORACLE Instance orcl1 – Archival Error. Archiver continuing.

有灾备库的主库报错 ORACLE Instance test- Archival Error. Archiver continuing.
查看METLAINK,解释如下:

The Problem here is that the Primary Database is switching Logs too frequently.

Using ARCH to send the archives, every time there’s a log switch the Primary has to send the Archivelog to the Standby, meanwhile another Log Switch occurred on the Primary which causes also another Archivelog to be sent to the Standby, but the first one has not finished yet, a GAP is formed and detected by the Standby. At this Time the first Archivelog is also sent as FAL Request, but this one will fail because the first one is still being archiving, locked, so the second one fails.

大概意思就是由于日志切换非常频繁(或者网络带宽不够),ARCH或者LSN正在进行日志传输,但是这个时候进行了日志切换从而导致可能的GAP检测到了,启动了另外的一个归档进程传输GAP归档到STANDBY端,但是这个时候实际上这个日志或者归档正在传输锁定了文件,所以第二个进程自然要报错。解决方法

Ignore these Messages as long as the Standby Database keeps synchronized with the Primary
Database Increase the Size of the Online Redologs to reduce Redolog Switch Frequency
Increase Network Bandwith between the Primary and Standby Database
只要备用数据库与主数据库保持同步,就忽略这些消息
数据库增加在线红皮书的大小,以减少红皮书切换频率
增加主数据库和备用数据库之间的网

本文固定链接: http://t.yjsec.com/index.php/2019/05/30/641/ | 下一站

该日志由 admin 于2019年05月30日发表在 ORACLE 分类下, 你可以发表评论,并在保留原文地址及作者的情况下引用到你的网站或博客。
原创文章转载请注明: ORACLE Instance orcl1 – Archival Error. Archiver continuing. | 下一站

ORACLE Instance orcl1 – Archival Error. Archiver continuing.:等您坐沙发呢!

发表评论

快捷键:Ctrl+Enter