FAL[server, ARCN]: FAL archive failed ORA-16401

今天資料庫日誌報警，然後檢視日誌報錯如下：
Sat Jun 07 17:35:19 2014
Archived Log entry 3272 added for thread 1 sequence 3224 ID 0xaad09f63 dest 1:
Sat Jun 07 17:35:36 2014
LNS: Standby redo logfile selected for thread 1 sequence 3225 for destination LOG_ARCHIVE_DEST_2
Sat Jun 07 17:35:39 2014
ARC0: Archive log rejected (thread 1 sequence 3224) at host 'yjfcores'
FAL[server, ARC0]: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance yjfcore - Archival Error. Archiver continuing.


trace記錄
*** 2014-06-06 11:48:12.502 4645 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16401 creating standby archive log file at host 'yjfcores'


*** 2014-06-07 15:56:21.520
kcrrwkx: unknown error:16401
Error 16401 creating standby archive log file at host 'yjfcores'


*** 2014-06-07 17:35:39.802
kcrrwkx: unknown error:16401

檢視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

謝謝！