8 Replies Latest reply: May 24, 2010 3:06 PM by 618702 RSS

    open failed for members of log group

    767555
      HI,

      OS : LINUX 5.1
      DB : 10.2.0.3

      i have configured physical standby and its working fine. but in alert log i m getting below error.
      i have checked the physical location of member. it is very much available.

      Mon May 24 23:54:19 2010
      Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
      ORA-00313: open failed for members of log group 1 of thread 1
      ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
      ORA-27037: unable to obtain file status
      Linux Error: 2: No such file or directory
      Additional information: 3
      Mon May 24 23:54:19 2010
      Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
      ORA-00313: open failed for members of log group 1 of thread 1
      ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
      ORA-27037: unable to obtain file status
      Linux Error: 2: No such file or directory
      Additional information: 3
      Clearing online redo logfile 1 /u001/app/oracle/oradata/YAHOO/redo01.log
      Clearing online log 1 of thread 1 sequence number 31
      Mon May 24 23:54:19 2010
      Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
      ORA-00313: open failed for members of log group 1 of thread 1
      ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
      ORA-27037: unable to obtain file status
      Linux Error: 2: No such file or directory
      Additional information: 3
      Mon May 24 23:54:19 2010
      Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
      ORA-19527: physical standby redo log must be renamed
      ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'

      can any one suggest?

      Regards,

      BK
        • 1. Re: open failed for members of log group
          sb92075
          can any one suggest?
          what clues exist in /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:

          post results from following commands

          ls -l /u001/app/oracle/oradata/YAHOO/redo01.log
          ls -ld /u001/app/oracle/oradata/
          ls -ld /u001/app/oracle/
          ls -ld /u001/app/
          ls -ld /u001/
          • 2. Re: open failed for members of log group
            618702
            Hi,

            Below note was taken from metalink;

            Symptoms
            Following errors in alert.log of standby database during startup of the standby database:

            ORA-00313: open failed for members of log group 1 of thread 1
            ORA-00312: online log 1 thread 1: '/u03/oradata/prod/redo01b.log'
            ORA-27037: unable to obtain file status
            Cause
            Online Redo logs missing on standby database.
            Solution

            You can safely ignore these messages. Online redo logs will be created automatically when you activate the standby after switchover or failover.

            If you want to fix these messages then please use following steps:

            1. Check and set "log_file_name_convert" parameter if the location of log files are different on primary and standby.
            SQL> alter system set log_file_name_convert = "'<location on primary>','<location on standby>'" scope=spfile;

            If you are using pfile then set the parameter in init file after shutting down the database:
            *.log_file_name_convert = '<location on primary>','<location on standby>'

            For 10gR2 only : Set this parameter even if the location of the redo logs are same on both primary and standby otherwise you may get ORA-19527 and ORA-312 while or after implementing the below steps.
            This is due to internal bug in 10.2.

            2. Cancel Managed Recovery process on the standby:
            SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

            3. Execute the command to clear all log groups on standby for each log group (for each log group):
            SQL>alter database clear logfile group 1;

            4. Check the v$log view to confirm the size and status.

            5. Recreate standby redo logs on standby (only if standby Redo logs are also missing) using:

            (a) Drop the standby redo logfile group(s) (check v$standby_log)
            SQL> alter database drop standby logfile group 4;

            (b) Recreate the standby logfile group(s)
            SQL> alter database add standby logfile group 4 ('/u03/redo/stby01.log') size 50m;

            Hope it helps you.
            • 3. Re: open failed for members of log group
              767555
              content in trace file is same as alert log:


              ORA-00313: open failed for members of log group 1 of thread 1
              ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
              ORA-27037: unable to obtain file status
              Linux Error: 2: No such file or directory
              Additional information: 3
              ORA-00313: open failed for members of log group 1 of thread 1
              ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
              ORA-27037: unable to obtain file status
              Linux Error: 2: No such file or directory
              Additional information: 3
              *** 2010-05-24 23:54:19.056 61283 kcrr.c
              Clearing online redo logfile 1 /u001/app/oracle/oradata/YAHOO/redo01.log
              ORA-00313: open failed for members of log group 1 of thread 1
              ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
              ORA-27037: unable to obtain file status
              Linux Error: 2: No such file or directory
              Additional information: 3
              ORA-19527: physical standby redo log must be renamed
              ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
              Error 19527 creating/clearing online redo logfile 1
              • 4. Re: open failed for members of log group
                618702
                You do not have any online redo logs on your standby database. That is why you are taking this error messages.

                Please can you check that your redo logs are there physically?

                Ogan
                • 5. Re: open failed for members of log group
                  767555
                  ogan,

                  redo logs are present in standby database....
                  • 6. Re: open failed for members of log group
                    618702
                    Do you have standby redo log files defined already with the same size as online redo log files?
                    • 7. Re: open failed for members of log group
                      767555
                      i do not have standby redo logs as i m in an impression that online redo log will serve the things....
                      • 8. Re: open failed for members of log group
                        618702
                        Here is a documentation from Oracle;

                        2.5.2 Standby Redo Logs

                        A standby redo log is similar in all ways to an online redo log, except that a standby redo log is used only when the database is running in the standby role to store redo data received from the primary database.

                        A standby redo log is required to implement:

                        * The maximum protection and maximum availability levels of data protection (described in Section 1.4 and in more detail in Section 5.6)
                        * Real-time apply (described in Section 6.2)
                        * Cascaded redo log destinations (described in Appendix C)

                        Configuring standby redo log files is highly recommended on all standby databases in a Data Guard configuration, because they provide a number of advantages:

                        * Because a standby redo log consists of preallocated files, a standby redo log avoids the operating system overhead of file system metadata updates common with sequential files (such as with an archive log).
                        * Standby redo log files can reside on raw devices, which may be important if either or both the primary and standby databases reside in a Real Application Clusters environment.
                        * Standby redo log files can be multiplexed using multiple members, improving reliability over archived log files.
                        * During a failover, Data Guard can recover and apply more redo data from standby redo log files than from the archived log files alone.
                        * The archiver (ARCn) process or the log writer (LGWR) process on the primary database can transmit redo data directly to remote standby redo log files, potentially eliminating the need to register a partial archived log file (for example, to recover after a standby database crashes). See Chapter 5 for more information

                        What is your data guard protection level?