Standby MRP stuck due to 'Archival Error' and ORA-16014 (Doc ID 2800690.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

No Error reported on Primary REDO transport,

Thread 1 advanced to log sequence 49 (LGWR switch)
Current log# 1 seq# 49 mem# 0: /<path>/group_1.277.896014167
Current log# 1 seq# 49 mem# 1: /<path>/group_1.276.896014173
Sun Aug 01 07:29:22 2021
******************************************************************
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_3
******************************************************************
Sun Aug 01 07:29:22 2021
Archived Log entry 12369 added for thread 1 sequence 48 ID 0xf4fa0568 dest 1:
LNS: Standby redo logfile selected for thread 1 sequence 49 for destination LOG_ARCHIVE_DEST_3

NOTE : Primary LNS shows shipping archived log SEQ# 49 but we see the archival error for SEQ 49. This issue is covered from database version 12c i.e any archival error on standby is captured in primary REDO transport itself.

Standby Alert log,

<>: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <SID> - Archival Error
ORA-16014: log 51 sequence# 49 not archived, no available destinations
ORA-00312: online log 51 thread 1: '/<path>/<SID>/redo_51a.log'
ORA-00312: online log 51 thread 1: '/<path><SID>/redo_51b.log'
Sun Aug 01 08:00:37 2021
Archiver process freed from errors. No longer stopped
Sun Aug 01 08:00:37 2021
RFS[1]: Selected log 57 for thread 1 sequence 57 dbid -620682547 branch 1079411824
RFS[1]: Selected log 59 for thread 1 sequence 58 dbid -620682547 branch 1079411824
RFS[1]: Selected log 60 for thread 1 sequence 59 dbid -620682547 branch 1079411824
Sun Aug 01 08:04:58 2021

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.