Stalk BrainSurface @

  • Facebook Page: 113995341985805
  • FeedBurner: brainsurface
  • Twitter: brainsurface
  • YouTube: brainsurface
  • External Link:

Like BrainSurface?

Joomla Templates and Joomla Extensions by JoomlaVision.Com

My SocialSurface

BlogSurface LIVE

Oracle R12 Financials ONLINE Training by highly experienced and versatile faculty.

New to Oracle Financials?? Get trained from the best instructor known  to have trained novices as experts in this field.  Training comes with exhaus ...

IOUG Virtualization SIG: Virtualization Events at COLLABORATE12

Virtualization Events at COLLABORATE 12 - IOUG Forum Sunday 4-5pm IOUG Virtualization SIG Meet and Greet (Surf F) 5-7pm IOUG We ...

Don’t let COLLABORATE12 slip away – Register NOW!

Special Registration Code : AP03 (Expires 04/06/2012) Registration URL: Sign Up, learn from and interact wit ...

Interview Question

Oracle Database Administration (DBA): 1. What is an Oracle Instance? 2. What information is stored in Control File? 3. When you start an Oracle DB ...

Building a new oracle server for practice

So i've been working on building my own home server and it was going well until I tested the components I purchased from new egg. I bought: MSI mo ...

Data Guard 10G Wizard: Standby creation fails with ORA-19527

Windows Server 2003: Oracle 10G Release 2: Data Guard Wizard in Grid Control fails and display error: ORA-19257: It reports creation status failed in the Data Guard Wizard spawned job with following errors in Standby alert log files:


ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: ‘\oradata\logs\redo01.log’

This entry was posted in BrainSurface, Data Guard, Database Family, Disaster Recovery, High Availability, Installation / Upgrades, Maximum Availability Architecture (MAA), My Blogs, Oracle Database Family, Tools / Utilities, Troubleshooting and tagged . Bookmark the permalink.

One Response to Data Guard 10G Wizard: Standby creation fails with ORA-19527

  1. Tariq says:

    Found the cause of the problem:

    Refer to Metalink Doc. 368693.1. This problem can occur on any platform with following errors in addition to above-mentioned ORA errors:

    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    ORA-19527 signalled during: ALTER DATABASE CLEAR LOGFILE GROUP 1
    Starting Data Guard Broker (DMON)

    Cause is internal Bug 5162803
    Solution mentioned is select OFA and customize filenames.

    Also please make sure that online redo log names for Standby database are not the same as the Primary database.

    If names are to be kept the same, please make sure that the path is different.

    If the select the option on the Standby of keeping the filename and locations the same as the Primary, the Standby database creation fails with above mentioned error messages.

    Best option is to convert your DB architecture to OFA (Optimal Flexible Architecture).

Leave a Reply