Redo logs member

we have four node primary database and 4 node stand by
created members on redo log group on the stand by database.
and thier status is
20 INVALID STANDBY /redo1/sckftprd/stndby_redo/redo20_c.log NO
21 INVALID STANDBY /redo2/sckftprd/stndby_redo/redo21_c.log NO
23 INVALID STANDBY /redo2/sckftprd/stndby_redo/redo23_c.log NO
22 INVALID STANDBY /redo1/sckftprd/stndby_redo/redo22_c.log NO
iam seeing continuos errors in the stand by alert log
ORA-00313: open failed for members of log group 21 of thread 2
Mon Sep 21 12:33:12 2009
ARC0: Archiving not possible: error count exceeded
Mon Sep 21 12:38:12 2009
Errors in file /opt/oracle/product/admin/SCKFTPRD/bdump/sckftprd4_arc0_16815.trc:
ORA-00313: open failed for members of log group 20 of thread 1
Mon Sep 21 12:38:12 2009
Errors in file /opt/oracle/product/admin/SCKFTPRD/bdump/sckftprd4_arc0_16815.trc:
ORA-00313: open failed for members of log group 21 of thread 2
Mon Sep 21 12:38:12 2009
Errors in file /opt/oracle/product/admin/SCKFTPRD/bdump/sckftprd4_arc0_16815.trc:
ORA-00313: open failed for members of log group 21 of thread 2
Mon Sep 21 12:38:12 2009
ARC0: Archiving not possible: error count exceeded
i havent created those members on primary does it cause any issue.....

We have no version number.
We have no idea what you created.
We have no idea what query produced the results you displayed.
We have no idea whether this has ever run or is a new installation.
We have no idea what you were trying to create ... physical or logical DG or just a standby.
We don't even know if the files Oracle is trying to open exist are have permissions allowing Oracle to read and write them
If you want help you need to post a lot more information. Else open an SR at metalink.

Similar Messages

  • Invalid redo log member

    Hi guys,
    i have 3 redo log groups with one member each with 50MB size in 10gR2 database on Windows.
    I added one more member in first group with also 50MB in size, but just when did that ,
    status of that new member has become invalid.
    Could You please comment this situation ?
    thx.

    thx guys , i managed with this thread :
    10g: Redo Log
    cheers,
    Toni

  • Redo log member

    How do I change the redo01.log destination?
    If I want change the path of redo01.log, do I copy the redo01.log to new destination and point at it.
    Or I just change the path and the new redo01.log will be automatically generated ?

    Do the following :
    1. Shutdown the database.
    2. Copy the logfile(s) to the new name/location at operating system level.
    3. Mount the database :  SQL> STARTUP MOUNT4. Rename the file(s) :  SQL> ALTER DATABASE RENAME FILE '<FULL PATH OF THE OLD LOGFILE>' TO '<FULL PATH OF THE NEW LOGFILE>';5. Open the database :  SQL> ALTER DATABASE OPEN;6. Remove the logfile(s) from the old location at the operating system level.

  • Groups and Member in Redo Log

    Hi,
    I would like to the defination and the functionality of Groups and Member in a Redo log file and also the distinction between them
    Thks

    Dear J.C.,
    The redo logs are files that the Oracle server uses to commit or rollback the transactions applied by the users.
    Redo Log files (minimum of two files) record all changes made to the database, hence ensuring that no data is lost in the event of a failure. In case of an instance failure, when the database is next started up, the Oracle server is automatically able to roll forward the transactions that were not applied when the database crashed and roll back the uncommitted transactions from the rollback segments. Hence the database recovers automatically to a consistent state that existed prior to the crash.
    A set of Redo Log files is called a Redo Log Group. Multiple copies (mirroring) of the Redo Log Files are used so as to protect the Redo Log Files from corruption / damage. Each Redo Log File in a Redo Log Group (called Redo Log Member) has essentially the same information, so if one is destroyed, another copy of that file is available for the Oracle server to use.
    Finally, the term Redo Log is used interchangeably with Redo Log Group.
    Ciao!

  • Online redo log files being removed physically

    Grid Infra version: 11.2.0.4
    RDBMS Version: 11.2.0.4
    Although this is a RAC DB, this is not a RAC-specific question. Hence posting it here.
    Few months back, I remember issuing a command similair to below (DROP LOGFILE GROUP ...) and the redo log files were still physically present in the diskgroup.
    If I remember correctly, the file is not deleted physical so that we can use the REUSE functionality (ALTER DATABASE ADD LOGFILE MEMBER '+REDO/orcl/onlinelog/redo1b.log' reuse to group 11; ) ie. you can use the REUSE command to add the logfile of the same name which is physically present in OS Filesystem/Diksgroup to redo log group.
    But today, after I issued the below command, I checked the diskgroup location from ASMCMD
    SQL> alter database drop logfile group 31;
    Database altered.
    From ASMCMD, I can that the file has disappeared physically. Is this a new feature with 11.2.0.4 or am I missing something here ?
    ASMCMD> ls +DATA/msblprd/onlinelog/group_31.548.833154995
    ASMCMD-8002: entry 'group_31.548.833154995' does not exist in directory '+DATA/msblprd/onlinelog/'

    Just to add to what Aman has said.
    It is a bad practice not to let OMF decide the placement of Online redo logs because of this issue especially when you use ASM.
    Executing rm command in Linux/Unix is easy but Dropping ASM aliases in the disk group can be a hassle.
    This is documented.
    "When a redo log member is dropped from the database, the operating system file is not deleted from disk. Rather, the control files of the associated database are updated to drop the member from the database structure. After dropping a redo log file, ensure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log file."
    http://docs.oracle.com/cd/E11882_01/server.112/e25494/onlineredo.htm#ADMIN11324
    BTW . You don't even need to set  db_create_online_log_dest_n to enable OMF for ORLs.
    SQL> show parameter log_dest
    NAME                                 TYPE        VALUE
    db_create_online_log_dest_1          string
    db_create_online_log_dest_2          string
    db_create_online_log_dest_3          string
    db_create_online_log_dest_4          string
    db_create_online_log_dest_5          string
    SQL> show parameter db_create_file_dest
    NAME                                 TYPE        VALUE
    db_create_file_dest                  string      +MBL_DATA
    alter database add logfile thread 4
    group 31 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 32 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 33 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 34 ('+MBL_DATA','+MBL_FRA') size 4096M ;
    Database altered.
    And redo logs will be neatly placed as shown below
       INST     GROUP# MEMBER                                             STATUS           ARC
             4         31 +MBL_DATA/bsblprd/onlinelog/group_31.276.832605441 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_31.297.832605445  UNUSED           YES
                       32 +MBL_DATA/bsblprd/onlinelog/group_32.547.832605451 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_32.372.832605457  UNUSED           YES
                       33 +MBL_DATA/bsblprd/onlinelog/group_33.548.832605463 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_33.284.832605469  UNUSED           YES
                       34 +MBL_DATA/bsblprd/onlinelog/group_34.549.832605475 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_34.359.832605481  UNUSED           YES

  • Redo Log Groups

    Call me stupid, but for some reason I've decided to get certified as a DBA even though I have always been a developer. Honestly, its not my fault. The choices in the development track are pretty boring...
    Anyway, while pouring through the Backup/Recovery documentation, I run across this:
    Every database must have at least two online redo log groups.
    Each redo log group contains at least one online redo log member,
    which is a physical file containing the redo records.I decided to check and see if I have "at least two online redo log groups" for my play database. Now, I am very very confused.
    I think this query shows my 3 log members, but for some reason the 1st column makes me think I have 3 log groups:
    select group#, member from v$logfile
        GROUP# MEMBER
             3 /var/opt/oracle/oradata/db92/redo03.log
             2 /var/opt/oracle/oradata/db92/redo02.log
             1 /var/opt/oracle/oradata/db92/redo01.logI only know of one place where my online redo is located:
    ls $ORACLE_BASE/oradata/db92
    redo01.log  redo02.log  redo03.logCan someone help me figure out if I have one-group and three-members??
    Any comments are welcome,
    Stan

    This information can help you:
    Adding Redo Log File Groups: Examples
    The following statement adds a redo log file group with two members and identifies it with a GROUP parameter value of 3:
    ALTER DATABASE
    ADD LOGFILE GROUP 3
    ('diska:log3.log' ,
    'diskb:log3.log') SIZE 50K;
    The following statement adds a redo log file group containing two members to thread 5 (in a Real Application Clusters environment) and assigns it a GROUP parameter value of 4:
    ALTER DATABASE
    ADD LOGFILE THREAD 5 GROUP 4
    ('diska:log4.log',
    'diskb:log4:log');
    Dropping Log File Members: Example
    The following statement drops one redo log file member added in the previous example:
    ALTER DATABASE
    DROP LOGFILE MEMBER 'diskb:log3.log';
    The following statement drops all members of the redo log file group 3:
    ALTER DATABASE DROP LOGFILE GROUP 3;
    Adding Redo Log File Group Members: Example
    The following statement adds a member to the redo log file group added in the previous example:
    ALTER DATABASE
    ADD LOGFILE MEMBER 'diskc:log3.log'
    TO GROUP 3;
    Renaming a Log File Member: Example
    The following statement renames a redo log file member:
    ALTER DATABASE
    RENAME FILE 'diskc:log3.log' TO 'diskb:log3.log';
    The preceding statement only changes the member of the redo log group from one file to another. The statement does not actually change the name of the file 'diskc:log3.log' to 'diskb:log3.log'. You must perform this operation through your operating system.
    Joel P�rez

  • Online Redo Log groups

    Dear All,
    How to check the health of redo log file, we have 200 MB undo tablespace in our production server is it enough for huge transactions. Can I check how much time my redo log file data have been overwritten?
    Further in which situation we will add Online Redo Log Groups and which situation we will add Log Members.
    My rollback segment is using System tablespace is it recommended?
    What is recommendation about 1 redo log group is redo log member or 1 redo log group is multiple redo log members.

    Thanks Mr. Nicolas. for your informative guidence.
    Can I check how much time my redo log file data have been overwritten?Check v$loghist.
    We have 218 records in v$loghist, it means 218 times data have been overwritten, i think its not good. Can you guide me how to rectyify this.
    in which situation we will add Online Redo Log GroupsIn case of checkpoint not complete reported into alert.log.
    How to findout checkpoint entry in alert.log
    which situation we will add Log Members.This is the redolog multiplexing, at least two members for each redolog group.
    Ok, Can we do multiplexing for members or just do for groups.
    My rollback segment is using System tablespace is it recommended?No.
    OK, can we change rollback segments tablespace.
    1 redo log group is redo log member or 1 redo log group is multiple redo log membersA minimum of two redolog group with two members for each.
    After, it depend of your db activity.
    We have just one member for each group and we have three groups, so whats ur recommnedation we will add 1 member in each group.

  • Why multiplex redo log group ?

    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    Salman

    Ansiktet wrote:
    EdStevens wrote:
    Salman Qureshi wrote:
    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    SalmanThe mirror won't protect you from an SA who deletes '/u01/oradata/redo01.log' because he is running out of space on /u01 and figures its safe to delete a log file.
    Or similar types of errors.
    The redo and control files are simply too critical to put all your eggs in one basket when planning their protection.:) Thats why you should not use Oracle default .log on redo, instead .dbf or .dbl can be used. THat's why I use the older (pre-10g) default of .rdo for redo logs
    However, has this happend anyone for real, that a SA delete Oracle files? Where do you think I came up with the example?
    HOw about an SA (or maybe the kind of "fresher" we often see here, Taking a look at a "log" file with notepad?
    If he is isnt stupid he should know that Oracle resides on /u01 partion (for example), and should not delete files there without consulting the DBA."should" is the operative word there. There is no accounting for corporate cultures and attitudes.
    But end the end, my example was to illustrate that not all problems with redo and control files are mitigated with disk mirroring.

  • INVALID redo log after creating a new group member

    Hi all,
    I've just followed instructions to create a new redo log file member:
    alter database add logfile member '/oracle/mplex/redo/redo01b.log' to group 1;
    When I query v$logfile, the status is INVALID though.
    SQL> select * from v$logfile where group# = 1;
    GROUP# STATUS TYPE
    MEMBER
    IS_
    1 ONLINE
    /u01/app/oracle/oradata/redo01.log
    NO
    1 INVALID ONLINE
    /oracle/mplex/redo/redo01b.log
    NO
    the oracle user owns the mplex directory and permission are fine
    [oracle@redo]$ ls -ltr
    total 51260
    -rw-r----- 1 oracle oinstall 52429312 Mar 11 11:55 redo01b.log
    Any ideas?
    Thanks

    connect to the database again as a sysdba, and run
    sql> alter system switch logfile;
    Run this command again.
    select * from v$logfile where group# = 1;
    You can get more information at http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm
    Edited by: pgoel on Mar 11, 2011 8:15 PM

  • Last valid member redo log

    hi all,
    what does this line means from the certification book.
    If the member you want to drop is the last valid member of the group, you cannot drop the member.

    You've got a group which is composed of two or more members. In order for it to be a group it must contain at leas one member, which becomes the last valid group member. If you try to remove it you will get this error:
    SQL> alter database drop logfile member 'F:\ORACLE\ORADATA\MARS\REDO03.LOG';
    alter database drop logfile member 'F:\ORACLE\ORADATA\MARS\REDO03.LOG'
    ERROR at line 1:
    ORA-00361: cannot remove last log member F:\ORACLE\ORADATA\MARS\REDO03.LOG for
    group 3

  • How to disable write to redo log file in oracle7.3.4

    in oracle 8, alter table no logged in redo log file like: alter table tablename nologging;
    how to do this in oracle 7.3.4?
    thanks.

    user652965 wrote:
    Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
    Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
    And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving.

  • Where RFS exactly write redo data ?  ( archived redo log or standby redo log ) ?

    Good Morning to all ;
    I am getting bit confused from oracle official link . REF_LINK : Log Apply Services
    Redo data transmitted from the primary database is received by the RFS on the standby system ,
    where the RFS process writes the redo data to either archived redo log files  or  standby redo log files.
    In standby site , does rfs write redo data in any one file or both ?
    Thanks in advance ..

    Hi GTS,
    GTS (DBA) wrote:
    Primary & standby log file size should be same - this is okay.
    1) what are trying to disclose about  largest & smallest here ? -  You are confusing.
    Read: http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_transport.htm#SBYDB4752
    "Each standby redo log file must be at least as large as the largest redo log file in the redo log of the redo source database. For administrative ease, Oracle recommends that all redo log files in the redo log at the redo source database and the standby redo log at a redo transport destination be of the same size."
    GTS (DBA) wrote:
    2) what abt group members ? should be same as primary or need  to add some members additionally. ?
    Data Guard best practice for performance, is to create one member per each group in standby DB. on standby DB, one member per group is reasonable enough. why? to avoid write penalty; writing to more than one log files at the standby DB.
    SCENARIO 1: if in your source primary DB you have 2 log member per group, in standby DB you can have 1 member  per group, additionally create an extra group.
    primary
    standby
    Member per group
    2
    1
    Number of log group
    4
    5
    SCENARIO 2: you can also have this scenario 2 but i will not encourage it
    primary
    standby
    Member per group
    2
    2
    Number of log group
    4
    5
    GTS (DBA) wrote:
    All standby redo logs of the correct size have not yet been archived.
      - at this situation , can we force on standby site ? any possibilities ? 
    you can not force it , just size your standby redo files correctly and make sure you don not have network failure that will cause redo gap.
    hope there is clarity now
    Tobi

  • Invalid standby redo log

    On standby database there is a standby log file with status
    invalid on ASM diskgroup. In the same log group there is a valid standby log file.
    I've tried to drop it and recreate it but its status is still invalid.
    Why the status of that file is invalid? It should be inaccessible
    to oracle somehow,but I can e.g. view properties of that file by EM db. control.

    Hi,
    After I clear the logfile, the invalid logfile member is delete from standby database.
    The alert log from standby database is:
    ORA-00313: open failed for members of log group 1 of thread 1
    Deleted Oracle managed file +FRA/PROJ_STD/onlinelog/group_1.948.766576659
    Deleted Oracle managed file +REDO01/PROJ_STD/onlinelog/group_1.288.766581971
    Deleted Oracle managed file +REDO02/PROJ_STD/onlinelog/group_1.288.766582015
    Completed: alter database clear logfile group 1What is correct? on primary and standby database must be equals about online redo logs?
    Why the Oracle delete the online log files that I add on standby?
    Thank you!!!!

  • Delete standby redo log from primary database

    Hi all,
    I'm trying to drop standby logfiles on primary database (other database that I'm configuring the DG).
    The members of the standby log groups don't exists on file system.
    Somebody have deleted these files. Its old configuration where the files were in file system. Now they are in ASM.
    When I try to drop the standby logfiles I got the following error:
    SQL> alter database clear logfile group 7;
    alter database clear logfile group 7
    ERROR at line 1:
    ORA-19528: redo logs being cleared may need access to files
    SQL> select * from v$logfile order by 1;
        GROUP# STATUS  TYPE    MEMBER                                                                           IS_
             1         ONLINE  +REDO1/proj/onlinelog/group_1.256.340558657                                     NO
             1         ONLINE  +REDO2/proj/onlinelog/group_1.256.340558659                                     NO
             2         ONLINE  +REDO1/proj/onlinelog/group_2.257.340558879                                     NO
             2         ONLINE  +REDO2/proj/onlinelog/group_2.259.340558879                                     NO
             3         ONLINE  +REDO1/proj/onlinelog/group_3.258.340558707                                     NO
             3         ONLINE  +REDO2/proj/onlinelog/group_3.257.340558709                                     NO
             4         ONLINE  +REDO2/proj/onlinelog/group_4.258.340558713                                     NO
             4         ONLINE  +REDO1/proj/onlinelog/group_4.259.340558711                                     NO
             5         ONLINE  +REDO2/proj/onlinelog/group_5.260.340558965                                     NO
             5         ONLINE  +REDO1/proj/onlinelog/group_5.260.340558963                                     NO
             6         ONLINE  +REDO1/proj/onlinelog/group_6.261.340558967                                     NO
             6         ONLINE  +REDO2/proj/onlinelog/group_6.261.340558967                                     NO
             7         STANDBY /oracle/proj/onlinelog2/redo_702.log                                            NO
             7         STANDBY /oracle/proj/onlinelog1/redo_701.log                                            NO
             8         STANDBY /oracle/proj/onlinelog2/redo_802.log                                            NO
             8         STANDBY /oracle/proj/onlinelog1/redo_801.log                                            NO
             9         STANDBY /oracle/proj/onlinelog2/redo_902.log                                            NO
             9         STANDBY /oracle/proj/onlinelog1/redo_901.log                                            NO
            10         STANDBY /oracle/proj/onlinelog1/redo_1001.log                                           NO
            10         STANDBY /oracle/proj/onlinelog2/redo_1002.log                                           NO
    20 rows selected.
    SQL> select * from v$standby_log order by 1;
        GROUP# DBID            THREAD#  SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
             7 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
             8 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
             9 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
            10 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0What can I do to drop these reference?
    Any other solution instead of edit the controlfile and stop/start tghe database?
    thank you!!!!

    Hello;
    Well Oracle thinks the files are there, but I remember a bug on metalink where the controlfile still had them, but they were not on the file system. Can you confirm they exist?
    Meanwhile I check my notes for the Oracle doc nunber.
    Bug 6128242: TRYING TO DROP STANDBY LOG FAILS WITH ORA-19528
    So if you are Oracle 10 this might be the issue.
    workaround is to re-create the controlfile without the incorrect logfile. ( Yuk!! )
    ORA-01156 When Adding Or Dropping Redo Logs [ID 452152.1]
    Best Regards
    mseberg
    Edited by: mseberg on Oct 31, 2011 5:09 PM

  • Resizing redo log files on a 3 node RAC with single node standby database

    Hi
    On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
    SQL> select group#,thread#,members,status from v$log;
    GROUP# THREAD# MEMBERS STATUS
    1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
    2 1 3 CURRENT & resized, switch logfile can change logfile group
    3 1 3 INACTIVE
    4 2 3 INACTIVE
    5 2 3 INACTIVE
    6 2 3 CURRENT
    7 3 3 INACTIVE
    8 3 3 INACTIVE
    9 3 3 CURRENT
    9 rows selected.
    SQL> alter database drop logfile group 1;
    Database altered.
    SQL> ALTER DATABASE ADD LOGFILE THREAD 1
    GROUP 1 (
    '/PROD/redo1/redo01a.log',
    '/PROD/redo2/redo01b.log',
    '/PROD/redo3/redo01c.log'
    ) SIZE 100M reuse; 2 3 4 5 6
    Database altered.
    However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
    SQL> select group#,member from v$logfile where type='STANDBY';
    GROUP#
    MEMBER
    10
    /PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
    11
    /PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
    12
    /PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
    Please let me know.
    Thanks
    Sumathy

    Hello;
    For Redo and Standby redo this won't help :
    standby_file_management is set to auto
    On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
    Then start recovery again.
    Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
    alter database add standby logfile group 4
    ('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
    ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
    Notes worth reviewing :
    Online Redo Logs on Physical Standby [ID 740675.1]
    Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
    Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
    Best Regards
    mseberg

Maybe you are looking for