主库的报警文件中有报错ORA-16401, ORA-16055

郑全

在主库联机日志切换频繁，在报警日志中，会发现 ORA-16401, ORA-16055 报错。具体见MOS

Doc ID 1243177.1

ORA-16401 and ORA-16055 reported in primary alert.log when redolog switch is over frequently (Doc ID 1243177.1)       

In this Document

Symptoms

Changes

Cause

Solution

References

APPLIES TO:

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Cloud Exadata Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later

Linux x86-64

SYMPTOMS

- ORA-16401 and ORA-16055 Error reported sometimes at Primary ALERT.LOG:

ARC3: Archive log rejected (thread 1 sequence 136480) at host '(DESCRIPTION=  (ADDRESS=(PROTOCOL=tcp)(HOST=XXX.XXX.X.XX)(PORT=1530))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(SERVER=DEDICATED)))'

Errors in file /<path>/trace/<db_name>_arc3_7445.trc:

ORA-16401: archivelog rejected by RFS

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

Errors in file /<path>/trace/<db_name>_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

There is no change made.

CAUSE

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.

Also check for the case explained in below note,

Ora-16401: Archivelog Rejected By Rfs (Doc ID 1183143.1)

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

REFERENCES

BUG:9848109 - ORA-16401: ARCHIVE LOG REJECTED BY REMOTE FILE SERVER

NOTE:1532566.1 - Handling ORL and SRL (Resize) on Primary and Physical Standby in Data Guard Environment