ORA-16086: Redo Data Cannot Be Written To The Standby Redo Log
(Doc ID 2281449.1)
Last updated on DECEMBER 06, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle 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
Information in this document applies to any platform.
Symptoms
========
Disclaimer:
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:
Primary:
DB Unique Name: PRIMARY - Net Connection Alias: PRIMARY
Standby:
DB Unique Name: STDBY
========
In primary database
SQL> SELECT RECOVERY_MODE database_mode, type, status FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2;
DATABASE_MODE TYPE STATUS
----------------------- ---------------- ---------
IDLE UNKNOWN ERROR
SQL> SELECT status, error FROM V$ARCHIVE_DEST_STATUS WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE' and DEST_ID=2;
STATUS ERROR
--------- -----------------------------------------------------------------
ERROR ORA-16086: Redo data cannot be written to the standby redo log
Changes
Primary database was restarted
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 |
Changes |
Cause |
Solution |