Standby Redo Logs are not Created when Creating a 9i Data Guard DB with RMAN
(Doc ID 185076.1)
Last updated on FEBRUARY 23, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 9.0.1 to 9.2]
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
Information in this document applies to any platform.
***Checked for relevance on 19-JUL-2010***
When creating a Data Guard (Standby) Database with RMAN standby recovery can
fail under the following conditions:
1. Standby Redo Logs had previously been added to the primary database.
2. You are using Guaranteed Protection Mode or Instant Protection Mode (LGWR SYNC
attributes in remote log_archive_dest destinations on primary).
With this configuration, the 9i Data Guard database gets successfully created
but recovery fails with the following errors:
Primary Alert Log:
LGWR: Transmitting activation ID 3261921794 (c26cfa02)
LGWR: Error 313 creating standby archive log file at host '<hostname>'
LGWR: Error 313 creating archivelog file '<archivelog_filename>'
LGWR: Completed archiving log 2 thread 1 sequence 9
Standby Alert Log:
Tue Apr 9 13:22:34 2002
Errors in file /<path>/<udump_directory>/<oracle_sid>_rfs_<pid>.trc:
ORA-313: open failed for members of log group 4 of thread 1
ORA-312: online log 4 thread 1: '/<path>/<logfilename.log>'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
The errors indicate that the standby redo logs do not physically exist on the
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!