Problem :

Sun Mar 29 17:47:42 2015
ARC0: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
ARC0: RFS network connection re-established at host 'pbldg'
ARC0: Archive log rejected (thread 1 sequence 4898) at host 'pbldg'
FAL[server, ARC0]: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance pbldb1 - Archival Error. Archiver continuing.
Sun Mar 29 18:00:00 2015

############################################################################

It is definitely not an archiving file system full. If it was the case then you would see archiver stuck messages in the alert log.

This is due to a bug and Oracle suggests to ignore these messages appearing in the Alert log as long as the Primary and Standby are in sync.

RC3: Archive log rejected (thread 1 sequence 136480) at host '(DESCRIPTION=  (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.26)(PORT=1530))(CONNECT_DATA=(SERVICE_NAME=sdbinfo)(SERVER=DEDICATED)))'

Errors in file /opt/dbinfo/diag/rdbms/dbinfo/dbinfo/trace/dbinfo_arc3_7445.trc:

ORA-16401: archivelog rejected by RFS

FAL[server, ARC3]: FAL archive failed, see trace file.

Errors in file /opt/dbinfo/diag/rdbms/dbinfo/dbinfo/trace/dbinfo_arc3_7445.trc:

ORA-16055: FAL request rejected

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance dbinfo - Archival Error. Archiver continuing.

- RedoLog switch happens very frequently before the above Error reported

- The requested ArchiveLog by FAL requests the current Log Sequence or the Sequence currently being archived

Changes

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.

Solution

    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

Source : http://scn.sap.com/thread/3351294