Standby redo log group for particular thread

hi masters,
actually i am performing an experiment to create physical standbyt database on the same machine as my primary database.
i ma going according to 'data guard admin guide'. while section for ading standby redo log group,it says that you have to add standby redo log group to "thread"....
what is this thread? and how can i foind to which thread i have to assign the next redo log group??
how can i find current thread??
what if i dont add "to thread' clause in my statement:-
ALTER DATABASE ADD STANDBY LOGFILE THREAD 5
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
thanks and regards
VD

Vikrant,
First a question: Do you have a RAC instance? If so the paragraph even doesn't apply to you and I'm not sure why you are questioning it.
Secondly
"The THREAD clause is required only if you want to add one or more standby redo log
file groups to a specific primary database thread. If you do not include the THREAD
clause and the configuration uses Real Application Clusters (RAC), Data Guard will
automatically assign standby redo log file groups to threads at runtime as they are
needed by the various RAC instances."
this means you dont have to specify thread for RAC,as it will allocate one according to current thread.
Your conclusion is incorrect.
Where do you read the word 'current'?
Oracle will likely simply make sure each instance has sufficient standby redolog groups, the requirement is 1 standby redolog group per group + 1 extra.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

  • Confused about standby redo log groups

    hi masters,
    i am little bit confuse about creating redo log group for standby database,as per document number of standby redo group depends on following equation.
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    but i dont know where to fing threads? actually i would like to know about thread in deep.
    how to find current thread?
    thanks and regards
    VD

    is it really possible that we can install standby and primary on same host??
    yes its possible and i have done it many times within the same machine.
    For yours confusion about spfile ,i agree document recommend you to use spfile which is for DG broker handling if you go with DG borker in future only.
    There is no concern spfile using is an integral step for primary and standby database implementation you can go with pfile but good is use spfile.Anyhow you always keep pfile on that basis you created spfile,i said you make an entry within pfile then mount yours standby database with this pfile or you can create spfile from this pfile after adding these parameter within pfile,i said cause you might be adding this parmeter from SQL prompt.
    1. logs are not getting transfered(even i configure listener using net manager)
    2.logs are not getting archived at standby diectory.
    3.'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION' NEVER COMPLETE ITS RECOVERY
    4. when tried to open database it always note it 'always' said system datafile is not from sufficiently old backup.
    5.i tried 'alter database recover managed standby database camncel' also.Read yours alert log file and paste the latest log here..
    Khurram

  • Standby Redo Log Groups

    I have a problem on my standby database.
    When I check the status of v$standby_log
    one loggroup by one is getting active.
    At the end all 15 loggroups have the status active and I get the message no logs of size #### available
    What is the reason that those logs are not written to disk ?
    MRP is running.
    database is in archivelogmode
    flashback is enabled
    Recover database using backup controlfile is not working
    archive log all not allowed the backup controlfile....

    This issue is normally found when the 'standby redo' log on the standby is not as large as the 'redo' log on the primary.
    Per oracle, all standby redo log size should be equal to or larger than the largest redo log on the primary database. Oracle recommends keeping all the redo logs and standby logs of the same size.
    Would you like to confirm all logs have been set as oracle mandates?
    Cheers.

  • Do I need to create new group for standby redo log files?

    I have 10 group of redo log files with 2 members for each group for my primary database , Do I need to create new group for standby redo log files for the standby database
    Group#     Members
    ==============
    1              2
    2              2
    3             2
    4             2
    5             2
    6             2
    7             2
    8             2
    9             2
    10           2
    If So, The following statment is correct? or nto
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 1 ('D:\Databases\epprod\StandbyRedoLog\REDO01.LOG',D:\Databases\epprod\StandbyRedoLog\REDO01_1.LOG');
    please correct me if am doin mistake
    becuase when I issue the statment I getting error message sayin the group is already created.

    Thanks John
    I just find the answer
    Yes, it's recomeded to add new group , for instnace If I have 10 group from 1 to 10 then the standby shoudl be from 11 to 20
    Thanks I found the answer.

  • Standby redo log does not exist...

    Hello,
    Oracle 11.2.0.2, running on Solaris
    This is kind of a continuation of a previous thread, but this is a different question:
    I have a DG configuration, with the primary database having 2 redo logs per redo log group.
    And, it has 2 redo logs for the standby redo log groups.
    But I just found out something very strange:
    For the standby redo log group, even though the database shows it has two redo log files per group, the second file does not actually exist on the file system.
    And, I have no idea where it is, or why the database is not complaining about it.
    See below:
    SQL> select * from v$logfile;
             GROUP# STATUS    TYPE    MEMBER                                        IS_
                 11           STANDBY /opt/oracle/oradata2/PROD/REDO01A_STDBY.log NO
                 11           STANDBY /opt/oracle/oradata3/PROD/REDO01B_STDBY.log NO    <== does not exist on file system
                 12           STANDBY /opt/oracle/oradata2/PROD/REDO02A_STDBY.log NO
                 12           STANDBY /opt/oracle/oradata3/PROD/REDO02B_STDBY.log NO    <== does not exist on file system
                 13           STANDBY /opt/oracle/oradata2/PROD/REDO03A_STDBY.log NO
                 13           STANDBY /opt/oracle/oradata3/PROD/REDO03B_STDBY.log NO    <== does not exist on file system
                 14           STANDBY /opt/oracle/oradata2/PROD/REDO04A_STDBY.log NO
                 14           STANDBY /opt/oracle/oradata3/PROD/REDO04B_STDBY.log NO    <== does not exist on file system
                 15           STANDBY /opt/oracle/oradata2/PROD/REDO05A_STDBY.log NO
                 15           STANDBY /opt/oracle/oradata3/PROD/REDO05B_STDBY.log NO    <== does not exist on file system
                  5           ONLINE  /opt/oracle/oradata1/PROD/REDO05A.log       NO
                  5           ONLINE  /opt/oracle/oradata2/PROD/REDO05B.log       NO
                  6           ONLINE  /opt/oracle/oradata1/PROD/REDO06A.log       NO
                  6           ONLINE  /opt/oracle/oradata2/PROD/REDO06B.log       NO
                  7           ONLINE  /opt/oracle/oradata1/PROD/REDO07A.log       NO
                  7           ONLINE  /opt/oracle/oradata2/PROD/REDO07B.log       NO
                  8           ONLINE  /opt/oracle/oradata1/PROD/REDO08A.log       NO
                  8           ONLINE  /opt/oracle/oradata2/PROD/REDO08B.log       NO
    18 rows selected.
    Notice below that the "B" redo logs do not exist.
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO01B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO01B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO02B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO02B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO03B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO03B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO04B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO04B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO05B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO05B_STDBY.log: No such file or directory
    But here, you can see that the "A" redo logs actually do exist.
    SQL> !ls -l /opt/oracle/oradata2/PROD/REDO01A_STDBY.log
    -rw-r-----   1 oracle   dba      536871424 Jan  7  2011 /opt/oracle/oradata2/PROD/REDO01A_STDBY.log

    Hello;
    I'm able to recreate
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             4         STANDBY /u01/app/oracle/oradata/RECOVER2/redo04.log        NO
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NOAnd then
    SQL> !ls -al /u01/app/oracle/oradata/RECOVER2/redo04.log
    ls: /u01/app/oracle/oradata/RECOVER2/redo04.log: No such file or directoryChecking... *Not there, but Oracle ( 11.2.0.3 ) allows clean up without barking. Had only one member so I did GROUP drop.
    SQL> ALTER DATABASE DROP LOGFILE GROUP 4;
    Database altered.
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NO
    SQL> Best Regards
    mseberg

  • Unassigned Status Of Standby Redo Log Files

    I created 2 standby redo log groups, and use LGWR in primary site to
    transfer redo data, all are good. But when I query the V$STANDBY_LOG
    view, I found that the status column of my both standby redo logs is UNASSIGNED".
    also sequence#
    THREAD# and all others are 0 and 0.
    Any explains.

    Thanks for the reply Sophie. I did perform log switch at my primary site but the status of standby redo log files remained unassinged. I am pasting here the message in my Alert Log file may be that can help you to diagonose the problem.
    ALTER DATABASE SET STANDBY DATABASE PROTECTED
    Tue Jul 26 15:35:18 2005
    Completed: ALTER DATABASE SET STANDBY DATABASE PROTECTED
    Tue Jul 26 15:35:22 2005
    ALTER DATABASE OPEN
    Tue Jul 26 15:35:23 2005
    LGWR: Primary database is in CLUSTER CONSISTENT mode
    LGWR: Primary database is in MAXIMUM PROTECTION mode
    LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
    LNS0 started with pid=18
    Tue Jul 26 15:35:28 2005
    LGWR: Error 16086 verifying archivelog destination LOG_ARCHIVE_DEST_2
    LGWR: Continuing...
    Tue Jul 26 15:35:28 2005
    Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
    ORA-16086: standby database does not contain available standby log files
    LGWR: Error 16086 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'TESTstdb'
    LGWR: Minimum of 1 applicable standby database required
    Tue Jul 26 15:35:28 2005
    Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
    ORA-16072: a minimum of one standby database destination is required
    LGWR: terminating instance due to error 16072
    Instance terminated by LGWR, pid = 1864

  • The file structure online redo log, archived redo log and standby redo log

    I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
    1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
    2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
    3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

    FZheng:
    Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
    But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
    My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
    This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
    Edited by: 853153 on Jun 22, 2011 9:42 AM

  • 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

  • Remove standby redo log, get ORA-00600

    Hi,
    My v$logfile
    GROUP# STATUS TYPE MEMBER
    IS_RECOVERY_DEST_FILE
    3 ONLINE /u01/app/oracle/oradata/orcl/redo03.log
    NO
    2 ONLINE /u01/app/oracle/oradata/orcl/redo02.log
    NO
    1 ONLINE /u01/app/oracle/oradata/orcl/redo01.log
    NO
    GROUP# STATUS TYPE MEMBER
    IS_RECOVERY_DEST_FILE
    4 STANDBY /u01/app/oracle/oradata/orcl/stdlog01.log
    NO
    5 STANDBY /u01/app/oracle/oradata/orcl/stdlog02.log
    NO
    And when i clear standby log 5
    SQL> alter database clear logfile group 5;
    alter database clear logfile group 5
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [2130], [0], [8], [2], [], [], [],[]
    Please help me :(

    This is the information
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    PL/SQL Release 11.1.0.6.0 - Production
    CORE 11.1.0.6.0 Production
    TNS for Linux: Version 11.1.0.6.0 - Production
    NLSRTL Version 11.1.0.6.0 - Production
    - Because the standby redo log group 5 is created with smaller size than the redo log. So, i want to remove this standby log and recreate the new one with equal or larger size of the online redo log
    Chuong

  • Adding bigger size Redo log groups In RAC , ASM

    Hi Folks,
    Database version - 10.1.0.4.0
    OS version - AIX 5.3
    RAC node 2 and ASM
    We had 4 redo log groups of lesser size on both nodes.yesterday I added 4 new groups of bigger size using pl/sql developer tool and deleted 2 old redolog groups. But I m not able to delete remaining 2 old groups.
    ORA-01567 dropping log2 would have less than 2 log files for instance 1.
    Our redolog files are on SAN and both node points to same storage. when I fired this query from command prompt
    SELECT v$logfile.member, v$logfile.group#, v$log.status, v$log.bytes
         FROM v$log, v$logfile
    WHERE v$log.group# = v$logfile.group#;
    I got same result for both nodes.
    The problem I suspect is that All the 4 new log groups are added to instance 2 and its 2 old grouips are are also deleted.
    Now my ques is that :
    1. shouild I have added redo log groups separately on both nodes even storage is same for both nodes ?
    2. redologs groups are defined separately for each node ?
    How should I assign 2 new redo log groups to instance 1 ?
    Regards,

    Please check:
    SQL> select instance_number, instance_name, thread# from gv$instance;
    Show Instance with thread ID
    SQL> select group#, thread#, members ,status from v$log;
    Check number groups in each of thread.
    On RAC, you have to add redo log Group each of node (each of thread )
    SQL> select group#, thread#, members ,status from v$log;
    From your environment ,I think you have 2 nodes = 2 thread
    If these're thread 1, 2
    So, add redo group should:
    Example:
    ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 11 ( '+DATA') SIZE 500M;
    ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 12 ( '+DATA') SIZE 500M;
    ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 13 ( '+DATA') SIZE 500M;
    ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 14 ( '+DATA') SIZE 500M;
    You should check each thread has >= 2 groups and that group had "INACTIVE" status before drop:
    SQL> select group#, thread#, members ,status from v$log;
    My Idea, you should have 3 redo log groups for each node(thread)
    Good Luck

  • Why do we need standby redo log on Primary database.

    Hi Gurus,
    I was going through the document in OBE,
    http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
    I have two queries:
    1) I noticed the statement -
    "Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
    Why do we have to create standby redo log on a primary database?
    2) There is another statement --
    "It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
    Why do we need one additional standby redo log group than in Primary database.
    Could anyone please explain to me in simple words.
    Thanks
    Cherrish Vaidiyan

    Hi,
    1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
    2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
    Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
    So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
    Regards
    Anudeep

  • Dataguard Solution for standby redo log file groups

    Respected Experts,
    My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.
    Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
    need to be created.
    Thanks and Regards
    Monoj Das

    My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.To configure standby either you can use duplicate target database for standby
    or
    1) restore standby controlfile
    2) mount standby database
    3) restore database
    and configure standby paraemter then start MRP, will do.
    http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
    Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
    need to be created.It depends which parameter you want to use, if you mention log_archive_dest_2='service ARCH ' then no need to create any standby redo log file groups,
    If you use log_archive_dest_2='service LGWR ' here transport will be in terms of redo and you need standby redo log files on standby database. Which is realtime.
    When you use LGWR, data lost will be less if in case of any online redo log file lost. which is recommended.
    HTH.

  • ORA-00313: open failed for members of log group 1 of thread 1

    Hi
    I'm restoring a database on a different host. I have the backups, from which I want to restore the database. I made the corresponding changes in the initSID.ora file and started the script to do the restore.These are the steps I followed:
    connect target=/
    run{
    startup nomount;
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    allocate channel c3 type disk;
    allocate channel c4 type disk;
    restore controlfile from '/tmp_backups/rman/lev0_open_cf_SID_2826_1';
    alter database mount;
    set newname for all datafiles
    restore database;
    set until logseq = 29317 thread = 1;
    switch datafile all;
    recover database;
    alter database open resetlogs;
    One mistake I made here is that logseq should have been last seq+1, which I did not do. I have it as last seq.
    Restore of datafiles and switching of datafiles was fine. But I get error for redo log files.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u13/oradata/SID/redo02a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Why is it looking for at the old path yet?
    I'm not sure what I missed and how to proceed. Please help.
    Thanks,
    Mamata

    I do believe that set newname for all datafiles only means actual datafiles and no redo logs. So with open resetlogs, Oracle tries to create new redo logfiles where the backup controlfiles says they are.
    As with creating a auxilliary database in another filesystem, we use DB_NAME_FILE_CONVERT and LOG_FILE_NAME_CONVERT.
    I am not sure if it is possible to type "set newname for all datafiles" and expect also the redo logfiles to change location.
    You might try to set these two parameters and see if it works.
    good luck.
    rgds
    Kjell Ove

  • ORA-00313: open failed for members of log group 3 of thread 1

    Whenever I try to login as a user I get the following:
    sqlplus user/user
    SQL*Plus: Release 10.2.0.2.0 - Production on Fri Nov 9 10:43:39 2007
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    So It occurs to me to login as sysdba and restart the DB …
    SQL> connect sys/manager as sysdba
    Connected.
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 536870912 bytes
    Fixed Size 1281264 bytes
    Variable Size 150995728 bytes
    Database Buffers 377487360 bytes
    Redo Buffers 7106560 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u06/oradata/RKDB/redo03.log'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    SQL> quit
    I now realized what happened and how this happened. During a clean-up effort this file was accidentally deleted and unfortunately we don’t have any backups.
    I am willing to lose the data. Is there something I can do so that the startup does not try to open this file ?
    All I am able to do now is to mount the database but not open it.
    Thanks in advance,
    Daniel

    this is what I get now ...
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL> Recover database until cancel;
    ORA-00279: change 608619 generated at 11/09/2007 10:00:41 needed for thread 1
    ORA-00289: suggestion : /u05/oradata/RKDB/arch/log1_33_633207859.arc
    ORA-00280: change 608619 for thread 1 is in sequence #33
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    '/u05/oradata/RKDB/arch/log1_33_633207859.arc'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL>

  • ORA-00313: open failed for members of log group 2 of thread 1

    We have a 4 node 32bit linux RAC (Dell/EMC) system running 9.2.0.4. It is very stable but over the past couple of months we've encountered a few ORA-00313 errors, while the system is running.
    No patterns. Different loads, times of day, nodes.
    The redo can't be opened, the node crashes, we look for errors, can't find any and then restart. The file is there and the permissions are fine. No other processes are accessing the files. No other Db errors. No O/S, SAN, Fiber, errors.
    All the research I've done shows that this is an error you'd only get on startup.
    We're going to log a TAR, but I can't believe we're the only ones to ever see this occur.
    [directory and server names have been modified to protect the system. Don't get hung up on typos or possible file system config problems too much - this system has been and is running now]
    ======================================================
    Log entries:
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    LGWR: terminating instance due to error 313
    Below are the contents of the trace file mentioned in the above log:
    trace file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    [oracle@db1 bdump]$ more /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/920
    System name: Linux
    Node name: db1.sample.com
    Release: 2.4.9-e.59enterprise
    Version: #1 SMP Mon Jan 17 07:02:16 EST 2005
    Machine: i686
    Instance name: sampdb1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 24
    Unix process pid: 2237, image: [email protected] (LGWR)
    *** SESSION ID:(25.1) 2005-10-11 22:31:02.315
    CMCLI WARNING: CMInitContext: init ctx(0xad96e80)
    *** 2005-10-24 22:51:58.192
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    error 313 detected in background process
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    ksuitm: waiting for [5] seconds before killing DIAG

    The only thing I can still think of is file permissions.
    If the system has recently been restored or Redo Log recreated, check the file permissions and ensure that Oracle has Read and Write Access to the Directory and Files.
    At least the file permissions on the directory and files should look something like this example
    $ls -l /sampledb/redo0/oradata/sampdb/
    drwxr-xr-x oracle oinstall 4096 19 May 17:46 redo
    $ls -l /sampledb/redo0/oradata/sampdb/redo/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:07 redo101.log
    $ls -l /sampledb2/redo0/oradata/sampdb/redo2/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:21 redo102.log
    $ls -l /sampledb3/redo0/oradata/sampdb/redo3/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:33 redo103.log

Maybe you are looking for