My Oracle Support Banner

ORA-16086: Redo data cannot be written to the standby redo log and RFS[368]: No standby redo logfiles selected (reason:7) (Doc ID 2356690.1)

Last updated on APRIL 24, 2023

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Database Unique Name: rmsdb_prd
Primary database: tccracdb
Standby database: racprdro
Configuration: dgconf1

************* 

Error: ORA-16810: multiple errors or warnings detected for the database

Warning: ORA-16857: standby disconnected from redo source for longer than specified threshold


ERROR ORA-16086: Redo data cannot be written to the standby redo log
RFS[368]: No standby redo logfiles selected (reason:7)

  Standby Database Alert.log

Archived Log entry 56 added for thread 1 sequence 3810 rlc 907769776 ID 0x7a27572d dest 2:

RFS[1]: No standby redo logfiles available for T-1 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
RFS[1]: Opened log for thread 1 sequence 3811 dbid 2049385006 branch 907769776
Wed Jan 03 16:43:37 2018
Archived Log entry 57 added for thread 2 sequence 4381 rlc 907769776 ID 0x7a27572d dest 2:
RFS[2]: No standby redo logfiles available for T-2 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
RFS[2]: Opened log for thread 2 sequence 4382 dbid 2049385006 branch 907769776
Wed Jan 03 16:49:54 2018

 

Primary Database Alert log

Wed Jan 24 08:55:58 2018
Errors in file /dbhome/oracle/diag/rdbms/tccracdb/tccracdb1/trace/tccracdb1_lgwr_25601.trc:
ORA-16086: Redo data cannot be written to the standby redo log

DataGuardBroker log

Error: The actual protection level 'Resynchronization' is different from the configured protection mode 'MaxAvailability'.
Redo transport problem detected: redo transport to database racprdro has the following error:
ORA-16086: Redo data cannot be written to the standby redo log
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration dgconf1 Warning ORA-16607
Primary Database tccracdb Error ORA-16810
Physical Standby Database racprdro Success ORA-00000

DataGuardBroker log

01/24/2018 08:59:49
Redo transport problem detected: redo transport to database racprdro has the following error:
ORA-16086: Redo data cannot be written to the standby redo log
01/24/2018 09:00:49
Redo transport problem detected: redo transport to database racprdro has the following error:
ORA-16086: Redo data cannot be written to the standby redo log

 

DGMGRL

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution


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