Drop LogFile

Hello I have Oracle 9, and I have a LogFile corrupt, message:ORA-00354 corrupt redo log block header, so I would like to drop this LogFile but i have next error: ORA-00350 log string of thread string needs to be archived, and I can not drop it,
Could you let me know what i can do?
Thank you

Hi..
alter database clear unarchived logfile '<logilename>';
Once done, take and keep a new fresh database backup, for recovery in future.If you have a dataguard of it you would need to make it again.
How many logfile members do you have in the group???
Anand

Similar Messages

  • Drop logfile group error!

    Hi,
    I got the following error while executing the statement:
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-00350: log 3 of thread 1 needs to be archived
    ORA-00312: online log 3 thread 1: 'F:\ORA9I\ORADATA\TESTDB\REDO03.LOG'
    Can anybody tell me the reason?
    TIA
    Aqueel.

    switch logs until the active one doesn’t belong to group 3.
    alter system switch logfile;
    Manually archive group 3
    alter system archive log GROUP 3;
    then drop group 3.
    alter database drop logfile group 3;
    Michel.
    www.odbtools.com

  • I want to increase logfile size?

    Good day,
    frequent log switches occuer in the database. the following message displays in OEM recommendations
    Increase the size of the log files to 327 M to hold at least 20 minutes of redo information.
    kindly telll me how to increase file size of logfile?
    thanks & Regards.

    to increase the size, create new log files, check point the old and drop.
    sql>select * from v$log
    sql>select * from v$controlfile_record_section where type ='REDO LOG'
    sql>alter database add logfile group 4 '/app/oracle/oradata/xxxx/redo04.log'
    size 350M reuse;
    sql>alter system switch logfile;
    sql>alter system checkpoint;
    Drop old logfiles.
    Alter database drop logfile group 1;
    note: if there are more than one gropus add same number of groups and delete all older groups

  • Query Regarding LOGFILES In Database

    *{color:#993366}Consider the following facts about database:*
    *{color}*
    {color:#ff00ff}{color:#0000ff}-The database is in NOARCHIVELOG mode
    -The database has three redologgroups.
    -All the groups have one member each.
    -Redolog3 is the current group.{color}
    {color}
    Now, we had executed the following command:
    SQL&gt;ALTER DATABASE DROP LOGFILE MEMBER
    2'D:\\ORACLE\\ORADATA\\MYDB\\REDOLOG3.LOG';
    The command fails to drop a member. What is the reason displayed for droping of the failure of the command?
    A)You cannot drop a member from a group as the database is in NOARCHIVELOG mode.
    B)You cannot drop the last member in a group.
    C)You cannot drop a member when a database is open.
    D)You cannot drop a member until checkpoint completes.

    user10182925 wrote:
    Hi Guys,
    I support with answer B only, Hope D is the correct answer if only two members were there...?Got confused why you are going to support with B?
    Yours scenario says that you have 3 redo log group and 3rd group is current..
    -The database has three redologgroups.
    -All the groups have one member each.
    -Redolog3 is the current group.Now according to above scenario
    SQL>ALTER DATABASE DROP LOGFILE MEMBER 2'D:\\ORACLE\\ORADATA\\MYDBREDOLOG3.LOG';The command fails to drop a member. What is the reason displayed for droping of the failure of the command?
    As yours redo log group 3 file is current which is being used ,unless DBWn writes all of those blocks that contained within this current log file then oracle no longer can reuse it nor can drop it.
    As far as concern with B
    B)You cannot drop the last member in a group.
    According to given scenario B,you can drop last redolog group if you have remaining group not less then 2 you have 3 redo log groups as well this redo log is other then current or active.
    Khurram

  • Lost Current Logfile

    Hi Friends. I cannot start my Instance because the Redo logfile current was deleted. I can startup mount but not open the database.
    I try:
    1. Alter system switch logfile, but database is not open
    2. alter tablespace drop logfile group 3 , but can not drop because is the current logfile.
    3. alter database clear logfile group 3, but said that is needed for crash recovery.
    4. alter database open resetlogs, but this option is valid after incomplete database recovery.
    5. alter database add logfile group 3 'c:\oracle\oradata\orcl\redo01.log', but said that group 3 already exists.
    6. I not have a backup for use RMAN.
    What I can do for open my database?
    Thaks a lot for any idea.

    Mr.Alfonso,
    If you have lost you current online redolog file then you need to mount the database and simulate a test recovery using the command
    RECOVER DATABASE UNTIL CANCEL;
    You might get some error since the log file is required for recovery.
    You need to issue the RECOVER CANCEL command and then open the database with the command
    ALTER DATABASE OPEN RESETLOGS;
    This would recreate the file for you.
    regards
    Yash Kapani

  • Need to drop a current redo log on a Standby

    Oracle 11.2.0.2
    I have 3 redo logs on a newly created Standby database.
    SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
    GROUP# ARC STATUS
    1 YES UNUSED
    3 NO CURRENT
    2 YES UNUSED
    The redo log in Group 3 needs to be dropped and recreated. How can I force a log switch on a Standby in mount mode?
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01623: log 3 is current log for instance ufms216 (thread 1) - cannot drop
    ORA-00312: online log 3 thread 1: '/path/redo03.dbf'
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    Please help !!!
    Thanks!
    Dave

    SAME ERROR/SITUATION
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 1.2527E+10 bytes
    Fixed Size 2231240 bytes
    Variable Size 3657434168 bytes
    Database Buffers 8858370048 bytes
    Redo Buffers 8691712 bytes
    Database mounted.
    SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
    GROUP# ARC STATUS
    1 YES UNUSED
    3 NO CURRENT
    2 YES UNUSED
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01623: log 3 is current log for instance ufms216 (thread 1) - cannot drop
    ORA-00312: online log 3 thread 1: '/a0253/d01/oradata/ufms216/redo03.dbf'
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    SQL> alter database recover managed standby database cancel;
    alter database recover managed standby database cancel
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not active
    SQL>
    HELP!

  • Dropping online redo!!!

    Dear all,
    your Views Pls...
    i've redo groups with two members each....
    if i delete one groups....will its Members will be deleted automatically.?..( i' using Oracle managed files structure..)
    one thing more ...after that i've to manually delete .rdo files from O/S..?
    ALTER DATABASE DROP LOGFILE GROUP 3;
    Thanx in Advance!!!

    hi,
    thanx for you suggestions..
    but alok....my senior has told me to do this..
    as i'm not going to do it directly....b'coz i know our prdn. DB...
    first i'll try to do this on my test DB...
    but...then what should i do now..i've to do it anyway?
    Thanx!!!

  • Post activity for drop & recreating log group

    Hi,
    We need to drop redolog group from old file system & going to recreate in different file system.
    ex,
    when group 3 is in "INACTIVE"
    alter database drop logfile group 3;
    alter database add logfile group 3 ('/u01/oracle/ica01/log3.ora,'/u01/oracle/ica02/log3.ora’ ) size 2G;
    Is there any post activity to update in control files or any other things ?
    Thx,
    Gowin.

    Osama_mustafa wrote:
    you need to rename logfile on OS Level "Physically" or you move them to another location.
    http://docs.oracle.com/cd/B28359_01/server.111/b28310/onlineredo004.htm
    That's if you are moving an existing file. The OP was asking about dropping an existing file and creating a new one. While the purpose may be the same (to relocate a file), the technique is vastly different and so the answer to his question is vastly different.
    To the OP: as you described your actions of dropping a redo log group and "recreating" it, the answer is no, there is no follow up work to be done. You did two logically un-connected actions:
    First, you dropped a redo log group. Fine. That is easily done online with no impact to the users and requires no follow-up actions.
    Second, you created a redo log group. Fine. That is easily done online with no impact to the users and requires no follow-up actions.
    The fact that the new redo log group has the same group name as the former - now non-existent - group is merely coincidental.

  • Cant drop a current redo log

    ORACLE 11.2.0.2
    I have a corrupted redo log on a Physical Standby db. The corrupted file is the current log. I cant do an "alter system switch logfile" because the database is not writeable.
    SQL> alter database open;
    Database altered.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
    Database altered.
    SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
    GROUP# ARC STATUS
    1 YES UNUSED
    2 YES UNUSED
    3 NO CURRENT
    SQL>
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-16000: database open for read-only access
    How can I drop log file #3? The database is currently a physical, if I convert ti to a logical, then the dp would be writeable. Would this work? Any other ideas??

    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm
    8.3.5 Adding or Dropping Online Redo Log Files
    Changing the size and number of the online redo log files is sometimes done to tune the database. You can add or drop online redo log file groups or members to the primary database without affecting the standby database. Similarly, you can drop log file groups or members from the primary database without affecting your standby database. However, these changes do affect the performance of the standby database after switchover.
    Caution:
    Whenever you add an online redo log file to the primary database, you should add corresponding online and standby redo log files to the standby database.
    For example, if the primary database has 10 online redo log files and the standby database has 2, and then you switch over to the standby database so that it functions as the new primary database, the new primary database is forced to archive more frequently than the original primary database.
    Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
    If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
    If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
    Add or drop an online redo log file:
    To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
    To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    Repeat the statement you used in Step 3 on each standby database.
    Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.

  • About the Restrictions of Dropping Online Redo

    Student Guide,7-13, If the database is running in ARCHIVELOG mode and the log file group to which the
    member belongs is not archived, then the member cannot be dropped.
    but:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination E:\oracle\admin\archive_log
    Oldest online log sequence 1043
    Next log sequence to archive 1045
    Current log sequence 1047
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME
    1 1 1044 1048576 1 YES INACTIVE
    1762339 2005-06-01 13:44:19
    2 1 1043 1048576 1 YES INACTIVE
    1762335 2005-06-01 13:44:12
    3 1 1045 1048576 2 NO INACTIVE (*****i want to delete group 3 member*****)
    1762344 2005-06-01 13:44:33
    4 1 1046 1048576 1 NO INACTIVE
    1762455 2005-06-01 13:46:11
    5 1 1047 1048576 1 NO CURRENT
    1762460 2005-06-01 13:46:23
    SQL> alter database drop logfile member
    2 .
    SQL> select * from v$logfile;
    GROUP# STATUS TYPE
    MEMBER
    1 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO01.LOG
    2 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO02.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG
    4 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO04.LOG
    5 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO05.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG (*****i want to delete group 3 member*****)
    6 rows selected.
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.
    LOG'
    2 /
    Database altered.
    SQL>
    it is done successfully, why?

    yes ,i drop group 3(ARCHIVED=NO STATUS=INACTIVE) ,it report ORA error ;
    and if drop member ("ARCHIVED=NO STATUS=CURRENT") , it report ORA error also.
    show:
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 NO INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 1 NO INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 NO INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-00350: log 3 of thread 1 needs to be archived
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG'
    Elapsed: 00:00:00.00
    SQL> alter database add logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.L
    OG' to group 3;
    Database altered.
    Elapsed: 00:00:02.03
    SQL> start reboot
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 34675092 bytes
    Fixed Size 453012 bytes
    Variable Size 25165824 bytes
    Database Buffers 8388608 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    Database opened.
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 NO INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 2 NO INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 NO INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> archive log start
    Statement processed.
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1049 1048576 1 YES INACTIVE
    1762943 2005-06-01 14:10:40
    2 1 1048 1048576 1 YES INACTIVE
    1762941 2005-06-01 14:10:39
    3 1 1050 1048576 2 YES INACTIVE
    1766105 2005-06-01 16:39:51
    4 1 1051 1048576 1 YES INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 NO CURRENT
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.02
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRS
    T_CHANGE# FIRST_TIME
    1 1 1054 1048576 1 YES INACTIVE
    1766281 2005-06-01 16:44:22
    2 1 1053 1048576 1 YES INACTIVE
    1766279 2005-06-01 16:44:19
    3 1 1055 1048576 2 NO CURRENT
    1766288 2005-06-01 16:44:37
    4 1 1051 1048576 1 YES INACTIVE
    1766107 2005-06-01 16:39:52
    5 1 1052 1048576 1 YES INACTIVE
    1766110 2005-06-01 16:39:52
    Elapsed: 00:00:00.00
    SQL> select * from v$logfile;
    GROUP# STATUS TYPE
    MEMBER
    1 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO01.LOG
    2 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO02.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG
    4 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO04.LOG
    5 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO05.LOG
    3 ONLINE
    E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG
    6 rows selected.
    Elapsed: 00:00:00.03
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.
    LOG'
    2 /
    alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.LOG'
    ERROR at line 1:
    ORA-01609: log 3 is the current log for thread 1 - cannot drop members
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03.LOG'
    ORA-00312: online log 3 thread 1: 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03B.LOG'
    Elapsed: 00:00:00.00
    SQL> alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.03
    SQL> alter database drop logfile member 'E:\ORACLE\ADMIN\WOSON\DATAFILE\REDO03b.
    LOG'
    2 /
    Database altered.
    Elapsed: 00:00:02.00
    SQL>

  • Dropping log file in standby database

    Please,
    I need a help for the following issue:
    I'm making a technical documentation on various event that occur on dataguard configuraation, right now I drop a redo log group file on primary database, and when I try to drop the equivalent log group file on standby database I got the following error:
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01156: recovery in progress may need access to files
    this is the current state of the redolog file on standby database.
    SQL> select group#,members,status from v$log;
    GROUP# MEMBERS STATUS
    1 3 CLEARING_CURRENT
    3 3 CLEARING
    2 3 CLEARING
    Eventhough I do the following command on standby I also get an error.
    SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
    ALTER DATABASE CLEAR LOGFILE GROUP 3
    ERROR at line 1:
    ORA-01156: recovery in progress may need access to files
    Can someone tell me how to drop on dataguard configuration the redolog file on primary database and their corresponding on standby database
    I'm working on 10 release 2, on Windows
    Thanks you

    Oracle Dataguard Concept and administration release 2,ref b14239: is my source but it doesn't work when trying to drop stanby group or logile member.
    For example, if the primary database has 10 online redo log files and the standby
    database has 2, and then you switch over to the standby database so that it functions
    as the new primary database, the new primary database is forced to archive more
    frequently than the original primary database.
    Consequently, when you add or drop an online redo log file at the primary site, it is
    important that you synchronize the changes in the standby database by following
    these steps:
    1. If Redo Apply is running, you must cancel Redo Apply before you can change the
    log files.
    2. If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO,
    change the value to MANUAL.
    3. Add or drop an online redo log file:
    ■ To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log'
    SIZE 100M;
    ■ To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    4. Repeat the statement you used in Step 3 on each standby database.
    5. Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
    Thank

  • Dropping Redo Log Members

    hi
    in Oracle documentation they said you can't drop a member if it's an active
    but i tried it in Oracle's Database 10g and it's dropped successfully
    what happend ?
    The link is :
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/onlineredo005.htm
    Thanks

    >
    but i tried it in Oracle's Database 10g and it's dropped successfully >
    You would have done alter system switch logfile before dropping the active redo logsfile.
    Refer to the link for the status of the redo logs [http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/dynviews_1126.htm#REFRN30127]
    23:36:05 venture >select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
             1          1         29  104857600          1 NO  INACTIVE               7457724 07-DEC-08
             2          1         30  104857600          1 NO  INACTIVE               7794484 08-DEC-08
             3          1         33  104857600          1 NO  CURRENT                8016830 09-DEC-08
             4          1         31  104857600          1 NO  INACTIVE               8016825 09-DEC-08
             5          1         32  104857600          1 NO  INACTIVE               8016827 09-DEC-08
    23:38:01 venture >create table test as select rownum id,'TEST' name from dual connect by level <= 10000000;
    Table created.
    Elapsed: 00:00:20.09
    23:39:27 venture >select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
             1          1         29  104857600          1 NO  INACTIVE               7457724 07-DEC-08
             2          1         30  104857600          1 NO  INACTIVE               7794484 08-DEC-08
             3          1         33  104857600          1 NO  CURRENT                8016830 09-DEC-08
             4          1         31  104857600          1 NO  INACTIVE               8016825 09-DEC-08
             5          1         32  104857600          1 NO  INACTIVE               8016827 09-DEC-08
    Elapsed: 00:00:00.00
    23:39:34 venture >alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01623: log 3 is current log for thread 1 - cannot drop
    ORA-00312: online log 3 thread 1: 'D:\ORACLE\ORADATA\VENTURE\REDO03.LOG'
    Elapsed: 00:00:00.01
    23:39:51 venture >alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.01
    23:40:02 venture >select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
             1          1         34  104857600          1 NO  CURRENT                8017910 09-DEC-08
             2          1         30  104857600          1 NO  INACTIVE               7794484 08-DEC-08
             3          1         33  104857600          1 NO  ACTIVE                 8016830 09-DEC-08
             4          1         31  104857600          1 NO  INACTIVE               8016825 09-DEC-08
             5          1         32  104857600          1 NO  INACTIVE               8016827 09-DEC-08
    Elapsed: 00:00:00.00
    23:40:03 venture >alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01624: log 3 needed for crash recovery of thread 1
    ORA-00312: online log 3 thread 1: 'D:\ORACLE\ORADATA\VENTURE\REDO03.LOG'
    Elapsed: 00:00:00.00
    23:40:11 venture >alter system switch logfile;
    System altered.
    Elapsed: 00:00:00.01
    23:40:25 venture >select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
             1          1         34  104857600          1 NO  INACTIVE               8017910 09-DEC-08
             2          1         35  104857600          1 NO  CURRENT                8018022 09-DEC-08
             3          1         33  104857600          1 NO  INACTIVE               8016830 09-DEC-08
             4          1         31  104857600          1 NO  INACTIVE               8016825 09-DEC-08
             5          1         32  104857600          1 NO  INACTIVE               8016827 09-DEC-08
    Elapsed: 00:00:00.00
    23:40:28 venture >alter database drop logfile group 3;
    Database altered.
    Elapsed: 00:00:00.00
    23:40:42 venture >select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
             1          1         34  104857600          1 NO  INACTIVE               8017910 09-DEC-08
             2          1         35  104857600          1 NO  CURRENT                8018022 09-DEC-08
             4          1         31  104857600          1 NO  INACTIVE               8016825 09-DEC-08
             5          1         32  104857600          1 NO  INACTIVE               8016827 09-DEC-08
    Elapsed: 00:00:00.00
    23:40:46 venture >HTH
    Anand

  • Drop log group of non existing thread

    How to drop an non-existing thread log group.
    My database doesn't have thread 3; this has been added during cloning from 3 node to 2 node RAC.
    alter database drop logfile group 10
    ERROR at line 1:
    ORA-01623: log 10 is current log for instance UNNAMED_INSTANCE_3 (thread 3) - cannot drop
    ORA-00312: online log 10 thread 3: '+DATA/devdb/onlinelog/group_10.560.811225745'
    ORA-00312: online log 10 thread 3: '+FLASHBACK/devdb/onlinelog/group_10.360.811225745'
    GROUP#    THREAD#     seq#    STATUS
    10                    3               1         ACTIVE             
    11                    3               0         UNUSED

    Hi,
    It seems that Group 10 of Thread 3 is still used as its status is current.
    Please try to do
    alter system switch logfile;
    alter system checkpoint;And see whats the status for thread 3 and also verify if really thread 3 is now required.
    And you can always disable this thread if now required.
    Thanks,
    Navneet

  • What will happen if I delete ACTIVE logfile member

    hi gurus
    JUST FOR TESTING.
    Consider the situation as follows
    I create a table,insert some rows into the table,then do a log switch. And then I remove the logfile which still in the "ACTIVE" states with operating system command.
    Finally I shutdown and restart the database, the database complains that the logfile group does not
    exist,so I drop the logfile group and open the database. I run a query against the table I created before,data still exists.
    The result of the test make me fell strange.
    Accornding to my knowledge, logfile in the 'ACTIVE' state means that the data protected by the logfile have not been written to the datafile.So I expect the table will not exists after I drop the logfile and then restart the database.
    Why the data are still there?
    Thanks a lot.

    hi Hashmi
    Testcase:
    SQL> select group#,status from v$log;
    GROUP# STATUS
    +1 INACTIVE+
    +2 INACTIVE+
    +3 CURRENT+
    SQL> select member from v$logfile where group#=3;
    MEMBER
    +/oracle/app/oracle/oradata/TESTDB/onlinelog/o1_mf_3_5tg3h0nz_.log+
    +/oracle/app/oracle/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_5tg3h29l_.log+
    SQL> drop table yef;
    Table dropped.
    SQL> create table yef as select * from system.maoxl;
    Table created.
    SQL> select group#,status from v$log;
    GROUP# STATUS
    +1 INACTIVE+
    +2 INACTIVE+
    +3 CURRENT+
    SQL>
    SQL> alter system switch logfile;
    System altered.
    SQL> select group#,status from v$log;
    GROUP# STATUS
    +1 CURRENT+
    +2 INACTIVE+
    +3 ACTIVE+
    SQL> host rm /oracle/app/oracle/oradata/TESTDB/onlinelog/o1_mf_3_5tg3h0nz_.log
    SQL> host rm /oracle/app/oracle/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_5tg3h29l_.log
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 2097152000 bytes
    Fixed Size                  2401464 bytes
    Variable Size             480947016 bytes
    Database Buffers         1593835520 bytes
    Redo Buffers               19968000 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/oracle/app/oracle/oradata/TESTDB/onlinelog/o1_mf_3_5tg3h0nz_.log'
    ORA-00312: online log 3 thread 1: '/oracle/app/oracle/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_5tg3h29l_.log'
    SQL> select group#,status from v$log;
    GROUP# STATUS
    +1 CURRENT+
    +3 INACTIVE+
    +2 INACTIVE+
    SQL> alter database drop logfile group 3;
    Database altered.
    SQL> alter database open;
    Database altered.
    SQL> select * from yef;
    ID
    +1+
    +4+
    +4+
    SQL>

  • Unable to drop a Redo Log Group

    Hi,
    My database is running on version 11.1.0.7 on OEL platform.
    I am trying to delete one of the Active Redo Log Group, it fails with the below error. Could someone please help me fix this issue?
    SQL >  select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARCHIVED  STATUS                                           FIRST_CHANGE# FIRST_TIME
            10          1       8017  524288000          2 YES       INACTIVE                                            1.2120E+13 17-JUN-2012 19:43:49
            11          1       8018  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 06:49:45
            12          1       8019  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 16:56:43
            13          1       8021  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:18:07
            14          1       8020  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:14:27
            15          1       8022  524288000          2 NO        CURRENT                                             1.2120E+13 19-JUN-2012 01:07:27
            16          2       6835  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:15:46
            17          2       6836  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:18:04
            18          2       6837  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:20:22
            19          2       6838  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:22:38
            20          2       6839  524288000          2 NO        CURRENT                                             1.2120E+13 19-JUN-2012 01:07:24
            21          2       6832  524288000          2 YES       INACTIVE                                            1.2120E+13 18-JUN-2012 23:11:45
            22          3       3771  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 22:04:11
            23          3       3772  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 23:55:55
            24          3       3773  524288000          2 YES       ACTIVE                                              1.2103E+13 09-SEP-2011 23:55:59
            25          3       3766  524288000          2 YES       INACTIVE                                            1.2103E+13 08-SEP-2011 22:05:29
            26          3       3767  524288000          2 YES       INACTIVE                                            1.2103E+13 08-SEP-2011 22:05:50
            27          3       3768  524288000          2 YES       INACTIVE                                            1.2103E+13 09-SEP-2011 14:02:05
    SQL > archive log list;
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /archive/MYCSMA/MYCSMA2
    Oldest online log sequence     6832
    Next log sequence to archive   6839
    Current log sequence           6839
    SQL > archive log all;
    ORA-00271: there are no logs that need archiving
    SQL > ALTER SYSTEM ARCHIVE LOG GROUP 24;
    ALTER SYSTEM ARCHIVE LOG GROUP 24
    ERROR at line 1:
    ORA-16013: log 24 sequence# 3773 does not need archiving
    SQL > alter database drop LOGFILE  group 24;
    alter database drop LOGFILE  group 24
    ERROR at line 1:
    ORA-01623: log 24 is current log for instance MYCSMA3 (thread 3) - cannot drop
    ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_1.log'
    ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_2.log'This was previously a 3 node RAC and when it was moved to a different machine, it got build with a 2-node RAC.
    Hence thread 3 is no more required. Thats why I am planning to drop these Redo Log Groups.
    Thanks!

    Hi;
    All information cover at:
    NOTE:102995.1 - Maintenance of Online Redo Log Groups and Members
    Regard
    Helios

Maybe you are looking for