Missing current redo log files

hello to all
i have a question please if you can guide me.
if i lose all current redo log files (current redo log group files) how i can repair it and open
database ? (i don't have problem by missing INACTIVE redo group)
thanks

Hi,
>>if i lose all current redo log files (current redo log group files) how i can repair it and
open database ? (i don't have problem by missing INACTIVE redo group)Well, It depends. The database was active when the current log file was lost ? Are you using RMAN ? The database is operating in ARCHIVELOG mode or NOARCHIVEMOG mode ? Basically, an incomplete recovery is necessary when there is a loss of the current redo log files. It means that you don’t have all the redo log files up to the point of failure, so the only alternative is[b] to recover prior to the point of failure. To perform incomplete recovery after the redo log files have been lost, you do the following (if you are not using RMAN):
1) Execute a SHUTDOWN command and restore all data files (*.dbf) from most recent backup.
2) Execute a STARTUP MOUNT command to read the contents of the control file.
3) Execute a RECOVER DATABASE UNTIL CANCEL command to start the recovery process.
SQL> startup mount;
4) Execute a RECOVER DATABASE UNTIL CANCEL command to start the recovery process.
SQL> recover database until cancel;
5) Apply the necessary archived logs up to, but not including, the lost or corrupted log.
6) Open the database and reset the log files.
SQL> alter database open resetlogs;
7) Shut down the database.
SQL> shutdown normal;
8) Take a full cold backup
In resume, for more information, take a look at [url http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen008.htm#sthref1872]Recovering After the Loss of Online Redo Log Files: Scenarios
Cheers
Legatti

Similar Messages

  • Current redo log file is lost

    Hi All,
    I got a scenario in which my current redo log file is lost:
    Do I need to:
    1)Clear log file group
    (or)
    2)I should perform incomplete recovery.
    What are the steps I should follow to recover this current redo log file?
    1)*If it is inactive* I can make use of
    ALTER DATABASE CLEAR LOGFILE UNARCHIVED GROUP 2;
    which will drop and recreate the log file.To recover from loss of an active online log group in NOARCHIVELOG mode:
    If the media failure is temporary, then correct the problem so that the database can reuse the group when required.
    Restore the database from a consistent, whole database backup (datafiles and control files) as described in "Restoring Datafiles Before Performing Incomplete Recovery". For example, enter:
    % cp /disk2/backup/*.dbf $ORACLE_HOME/oradata/trgt/
    Mount the database:
    STARTUP MOUNT
    Because online redo logs are not backed up, you cannot restore them with the datafiles and control files. In order to allow the database to reset the online redo logs, you must first mimic incomplete recovery:
    RECOVER DATABASE UNTIL CANCEL
    CANCEL
    Open the database using the RESETLOGS option:
    ALTER DATABASE OPEN RESETLOGS;
    Shut down the database consistently. For example, enter:
    SHUTDOWN IMMEDIATE
    Make a whole database backup.
    To recover from loss of an active online redo log group in ARCHIVELOG mode:
    If the media failure is temporary, then correct the problem so that the database can reuse the group when required. If the media failure is not temporary, then use the following procedure.
    Begin incomplete media recovery, recovering up through the log before the damaged log.
    Ensure that the current name of the lost redo log can be used for a newly created file. If not, then rename the members of the damaged online redo log group to a new location. For example, enter:
    ALTER DATABASE RENAME FILE "?/oradata/trgt/redo01.log" TO "/tmp/redo01.log";
    ALTER DATABASE RENAME FILE "?/oradata/trgt/redo01.log" TO "/tmp/redo02.log";
    Open the database using the RESETLOGS option:
    ALTER DATABASE OPEN RESETLOGS;
    My question is when the redo log file is current. What steps we should follow?
    Best regards,
    Rafi.
    http://rafioracledba.blogspot.com/
    2)If it is active then I can make use of below steps:

    Rafi (Oracle DBA) wrote:
    Hi Asif,
    This link I have seen by refering to previous post.I just have a slight doubt in mind.
    1)Do I need to make use of statement:
    Alter database clear unarchived log file group#;
    (or)
    Only if your group is current(or you are not able to drop it) and is not archived then you should use above query.
    We should perform incomplete recovery for this.If we have to perform incomplete recovery what are the steps I should follow?
    I doubt you should be performing incomplete recovery for this.
    Eg:Let us say my group 1 is dropped it has only one member and it is in active state.How to recover database?Can I get the steps?
    You would not be able to drop it if it is in active state, did you meant it is corrupted? If yes then you can use below query
    Alter database clear [unarchived] LOGFILE GROUP #;>
    Best regards,
    Rafi
    http://rafioracledba.blogspot.com/
    Make sure to backup your database after above activity.
    Regards
    Anurag

  • Redo log file corupted, database not getting open

    I am Oracle Funda-1 student.
    Have install standard Oracle 9I on Windows XP pro service pack 2.
    I made some changes in sample table & given commit. So log buffer will flush to redo log file.
    Then I open current redo log file from OS & selected all junk characters [select all] & deleted same. Save the file. Causing redo file size 0KB.
    Then made more changes to table & issue commit. no errors ! every thing working file.
    Even chked V$log & V$logfile.
    Again I open current redo log file from OS & selected all junk characters [ select all ] & deleted same. Save the file. Causing redo file size 0KB.
    Then issue manual log switch. Alter system switch logfile
    I got disconnected from database & database was close.
    When I reconnected & try to open database in normal mode. Gave error saying redolog_1.log is corrupted & needed for recovery.
    Now not even allowing me clear redo group 1. with alter database clear logfile group 1. as database is not coming to open stage.
    just able to mount the database. with error rdolog_1 corrupted.
    Wasn't oracle suppose to be halted when very 1st time I corrupted redo log file.
    Why it disconnected me & got close.
    When then one use alter database clear logfile group 1.

    I may try this ALTER DATABASE OPEN RESETLOGS;
    As no backup & not multiplex.
    Still looking for explanation why database got close down instead of getting halt.
    I have found one more status in V$log, which is not given in Oracle university book or online document.
    INVALIDATED
    Which come as a result when oracle unable to switch to next on line group due to non availability of next group redo log physical file.
    SQL> select group#,members,status from V$log;
    GROUP# MEMBERS STATUS
    1 1 INVALIDATED
    2 1 INACTIVE
    4 1 UNUSED
    As matter of fact, it's only portion of a big
    document which happen to cover what you are testing
    in detail.
    I would invest time to read the document to
    understand how things work instead of getting dirty
    quick answers.

  • Problem in creating database -Missing Redo log file

    I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
    My alert log file is
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:27 2013
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:38 2013
    Setting recovery target incarnation to 2
    Wed Nov 06 10:07:38 2013
    Assigning activation ID 1876274518 (0x6fd5ad56)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
    Successful open of redo thread 1
    Wed Nov 06 10:07:38 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Wed Nov 06 10:07:38 2013
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc  (incident=1345):
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
    Wed Nov 06 10:07:46 2013
    Trace dumping is performing id=[cdmp_20131106100746]
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Error 600 happened during db open, shutting down database
    USER (ospid: 5424): terminating the instance due to error 600
    Instance terminated by USER, pid = 5424
    ORA-1092 signalled during: alter database "oracl" open resetlogs...
    ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
    Wed Nov 06 10:07:47 2013
    ORA-1092 : opitsk aborting process
                                                                                                                                   251,1         95%

    >I am try to create a new database using DBCA
    >Please help me to resolve this issue.My redo log file was missing
    DROP and recreate the database.  It is a *new* database without any data.
    Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
    Hemant K Chitale

  • Commit Completes although current online redo log file have been removed.

    Although i have removed current online redo log file in linux os (Oracle Linux),when i type "commit" it says that "commit complete".
    Is this fair for this princip?*:" if Only when all redo records associated with a given transaction are safely on disk in the online logs is the user process notified that the transaction has been committed."*
    I think that it can lead to loss of data in some cases..I'm using Oracle 11g R2 on OEL (x64)..
    Can anyone explain me ? I'm getting stuck in this situation..
    P.S : I haven't multiplexed current ORL group files...

    Javid wrote:
    Although i have removed current online redo log file in linux os (Oracle Linux),when i type "commit" it says that "commit complete".
    Is this fair for this princip?*:" if Only when all redo records associated with a given transaction are safely on disk in the online logs is the user process notified that the transaction has been committed."*
    I think that it can lead to loss of data in some cases..I'm using Oracle 11g R2 on OEL (x64)..
    Can anyone explain me ? I'm getting stuck in this situation..
    In *nix, a file that is open by a process isn't really deleted until the process that has it completes.  So even though you 'deleted' a redo log, oracle is still holding it.  As soon as you stop your database (maybe even as soon as the db does a log switch) the redo will really be gone and no longer available.  consider the implications for archive logging.
    P.S : I haven't multiplexed current ORL group files...You need to fix that. the online logs are the achilles heel of the database. That's why it is standard practice to multiplex them.

  • Recover from missing files(redo log file/control file) and state of the DB

    Hello,
    i hv go through the doc. as well. But have some doubts what will happen in each on these situations.
    Pls help me to clarify these!
    Scenario is like this;
    hv 3 redo log files - multiplxed
    hv 3 control files - multiplxed
    - What will happen if 1 redo log file missing when starting the DB?
    - What will happen if 1 redo log file missing when using(performing operations) the DB?
    (will it recover automatically/db abort/even redo log lost will the DB run as usual... ?)
    -How to recover this lost redo log?
    - What will happen if 1 control file missing when starting the DB?
    - What will happen if 1 control file missing when using(performing operations) the DB?
    (will it recover automatically/db abort/even control file lost will the DB run as usual... ?)
    -How to recover this lost redo log?
    thanks

    - What will happen if 1 redo log file missing when starting the DB?IF you have multiplexed the members you can drop the lost file and will be able to open the DB
    What will happen if 1 redo log file missing when using(performing operations) the DB?Again if multiplexed it will drop a warinign in the alert log and contnue to write on othere members
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen.htm#sthref1385
    - What will happen if 1 control file missing when starting the DB?Just remove the entry from the init.ora and start the DB
    What will happen if 1 control file missing when using(performing operations) the DB?Will shutdown

  • Removing Redo Log Files? What's Normal?

    Hello,
    I'm new to Oracle and I've been using Informix for years. We currently have Oracle 9.2 running on Windows 2000 Server machine and apparently the redo log files keep filling up the disk drives they reside on. This is happening about every two weeks since we go out and delete the files when we remember.
    My question is does Oracle have a "normal" way of removing old redo logs automatically rather than having to remove them manually? In the Informix world I can set the logical logs so that they write over previously used logs once they are no longer used. Is there a similar way to configure Oracle?
    Thanks for helping out.
    Gregg Walker

    Do not delete your old log files: you need them.
    That's how Oracle does recovery when you lose a datafile or a drive. You copy over the missing stuff from your back-up and then Oracle re-applies the chnages from the REDO logs thereby bringing your database back up to date. No work lost. Result!
    Of course, if you don't take up a backup then holding on to REDO logs is pointless. In which case, set the database to run in NOARCHIVELOG mode.
    However, I strongly advise you to run in ARCHIVELOG mode. You may find this part of the administrator's guide informative: http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/archredo.htm#4553
    Cheers, APC

  • How to remove a redo log file

    Hi Experts,
    I want to remove a wrong redo log file from 10G R2 database in window.
    how to do that without loss data?
    my steps as
    1. alter system switch logfile;
    2. select * from v$log;
    which ARC and sataus do I can drop redo log file based on above SQL
    no archive and active status?
    ALso Which account should I do above action?
    fExamp, system account added redo log file, i only
    can drop by system? how about sys?
    Thanks help in detail steps
    Jim
    Edited by: user589812 on Dec 23, 2008 4:35 PM

    Jim,
    Check this link out for how to drop a redo log file
    Make sure a redo log group is archived (if archiving is enabled) before dropping it. To see whether this has happened, use the V$LOG view.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#i1006489
    SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
       GROUP# ARC STATUS
            1 YES ACTIVE
            2 NO  CURRENT
            3 YES INACTIVE
            4 YES INACTIVE
    Drop a redo log group with the SQL statement ALTER DATABASE with the DROP LOGFILE clause.
    The following statement drops redo log group number 3:
    ALTER DATABASE DROP LOGFILE GROUP 3;

  • Restore in noarchivelog mode ( redo log files have been dropped )

    1, A full backup taken using RMAN is available on disk.
    2, The current control files were NOT damaged and do not need to be restored.
    3, All data files are damaged .
    4, The database is in NOARCHIVELOG mode.
    I restore database :
    1. RMAN> STARTUP MOUNT
    2. RMAN> RESTORE DATABASE;
    3. RMAN> recover database;
    in this step , I got the information about needing redo log files ; but the redo log
    files have been dropped , what should i do ?
    else
    I want to know there is the command 'recover database using backup control file'
    in rman or not ?
    Tks

    Possibly loss of data (because information in online redo logs is lost):
    recover database until cancel;
    (cancel immediately)
    alter database open resetlogs; (to build a new set of redo logs)
    It's not necessary to use a backup controlfile here.

  • Why it automatically recover current redo log in RMAN command window?

    Firstly, I restore controlfile and datafiles from a backupset.
    Then when I recover database in RMAN command window like below:
    RMAN> recover database;
    Starting recover at 15-AUG-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc
    archive log thread 1 sequence 10 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc
    archive log thread 1 sequence 11 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc
    archive log thread 1 sequence 12 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc
    archive log thread 1 sequence 13 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc
    archive log thread 1 sequence 14 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc
    archive log thread 1 sequence 15 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc
    archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15
    archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16
    media recovery complete, elapsed time: 00:00:04
    Finished recover at 15-AUG-13
    RMAN>
    But, when I recover database in SQL*Plus command window like below:
    [oracle@lonion ~]$ uniread sqlplus /nolog
    [uniread] Loaded history (2178 lines)
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    SQL> conn /as sysdba
    Connected.
    SQL>
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a
    rc
    ORA-00280: change 2147842454 for thread 1 is in sequence #9
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.
    arc
    ORA-00280: change 2147842651 for thread 1 is in sequence #10
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd
    0slz_.arc' no longer needed for this recovery
    ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.
    arc
    ORA-00280: change 2147842653 for thread 1 is in sequence #11
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s
    d0tsb_.arc' no longer needed for this recovery
    ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.
    arc
    ORA-00280: change 2147842656 for thread 1 is in sequence #12
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s
    d110b_.arc' no longer needed for this recovery
    ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.
    arc
    ORA-00280: change 2147842684 for thread 1 is in sequence #13
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s
    d2ksr_.arc' no longer needed for this recovery
    ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.
    arc
    ORA-00280: change 2147842686 for thread 1 is in sequence #14
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s
    d2mc6_.arc' no longer needed for this recovery
    ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.
    arc
    ORA-00280: change 2147842689 for thread 1 is in sequence #15
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s
    d2qrm_.arc' no longer needed for this recovery
    ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.
    arc
    ORA-00280: change 2147842691 for thread 1 is in sequence #16
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s
    g0or9_.arc' no longer needed for this recovery
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s
    g0os5_.arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo01.log        ---- Yon see, proceeding this process, it can't automatically apply the current redo log.
    Log applied.
    Media recovery complete.
    SQL>
    Question Coming:
    Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?
    BTW: Please pay attention to the red font.

    It also seems not work.
    SQL> recover automatic database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file
    or directory
    Additional information: 3
    SQL>
    It must specify the redo log.
    SQL> recover database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo02.log
    Log applied.
    Media recovery complete.
    SQL>

  • Errors reported in alert log file regarding redo log files

    Hi,
    In my database i see the following entries regarding the redo log files frequently.
    Thread 1 advanced to log sequence 88
    Current log# 3 seq# 88 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\PELICAN\REDO03.LOG
    Thread 1 advanced to log sequence 89
    Current log# 1 seq# 89 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\PELICAN\REDO01.LOG
    Thread 1 cannot allocate new log, sequence 90
    Checkpoint not complete
    I have 3 redo log files of 50MB each. My database is 10g.
    What is the reason?
    What do i need to do ?
    Thanks.

    Hi,
    It is clearly stated that checkpoint is not complete. Thats why it could not allocate new sequence number to group 1.
    We can understand that your redo log group size is insufficient. or increase the number of redo log groups.
    Just test adding one more redo log group or test by increasing the size of redo log groups.

  • 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

  • Use of standby redo log files in primary database

    Hi All,
    What is the exact use of setting up standby redo log files in the primary database on a data guard setup?
    any good documents?

    A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
    You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.
    refer the link,and Perform the following steps to configure the standby redo log.:-
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
    If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
    refer the link
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1023371

  • Redo log files lost in Disk Corruption/failure

    DB version:10gR2
    In one of our test databases, I have lost all members of a group due to disk corruption(it was a bad practise to store both members on the same filesystem)
    Database is still up. We don't have a backup of the lost redo log group. Altogether we had 3 redo log groups. this is what i am going to do to fix this issue.
    Step 1. Add a redo log group
    ALTER DATABASE
    ADD LOGFILE ('/u04/oradata/ora67tst/log4a.rdo',
       '/u05/oradata/ora67tst/log4b.rdo') SIZE 15m;Step 2. Drop the corrupted redo log group
    ALTER DATABASE DROP LOGFILE GROUP 2;Is this the right way to go about fixing this issue?
    The documentation says that you need to make sure a redo log group is archived before you DROP it.
    When i use the query
    SQL>SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
        GROUP# ARC STATUS
             1 YES  ACTIVE
             2 NO  CURRENT
             3 NO  INACTIVE
    How can i force the archiving of a redo log group 2?
    Edited by: Citizen_2 on May 28, 2009 10:10 AM
    Edited by: Citizen_2 on May 28, 2009 10:11 AM

    Citizen_2 wrote:
    How can i force the archiving of a redo log group 2?How could you archive a log group when you have lost all members of that group?
    Have you checked out this documentation: [Recovering After the Loss of Online Redo Log Files|file://///castle/1862/Home%20Directories/Vaillancourt/Oracle%2010gR2%20Doc/backup.102/b14191/recoscen008.htm#sthref1872]
    More specifically:
    If the group is . . .      Current      
    Then . . .
    It is the log that the database is currently writing to.
    And you should . . .
    Attempt to clear the log; if impossible, then you must restore a backup and perform incomplete recovery up to the most recent available redo log.
    >
    HTH!

  • Increase current redo log size in standby database in mount stage

    We have oracle 10g standby database. The standby database is always running in mount stage while apply logs manually not data guard is used.
    We have increase size or online redo log in primary . Now want to inrease in standby database also.
    how to increase the size of current online redo log in standby database while it in mount stage .
    in mount stage we cant run alter system switch logfile

    user11965804 wrote:
    We have oracle 10g standby database. The standby database is always running in mount stage while apply logs manually not data guard is used.
    We have increase size or online redo log in primary . Now want to inrease in standby database also.
    how to increase the size of current online redo log in standby database while it in mount stage .
    in mount stage we cant run alter system switch logfilein 10g Standby will be always in Mount status when MRP is running.
    When you increase size of online redo log files in primary, You should increase in standby also..
    Standby redo log file size should be equal or higher than primary. You no need to switch log files on Standby.
    You will have only standby redo log files in standby not ORL(online redo log files)
    You can use this below script to add standby redo log files.
    http://www.pythian.com/news/581/oracle-standby-redo-logs/

Maybe you are looking for

  • HT201371 There is no longer a TouchID item on my 5s - why? How to get it back?

    I used the TouchID then started to use only a code. Now after a while there no possibility to create a TouchID What to do?

  • MM Request For Quotation Condition tables

    Hi experts,   I am writing a Report, which i have requirment like Comparision of Vendor Quotations, for this i need MM Quotation condition tables, I was searching for knumv in EKKO table but the value was not updating in EKKO. please tell me where i

  • BSP Exception: Das Objekt search.htm in der URL /sap/bc/bsp/sap/webserviceb

    Hi I am trying to open web service using outside in approach http://host:httpport/sap/bc/bsp/sap/webservicebrowser/search.html its giving exception sayin BSP Exception: Das Objekt search.htm in der URL /sap/bc/bsp/sap/webservicebrowser/search.htm ist

  • Installing Bi content errors

    Hi, I am trying to install Bi content and i get many errors, can someone tell me what this means and the solution to it, Characteristic 0soursystem must equally be a navigational attribute of  charac  0asset characteristic 0asset: attribute 0plant co

  • Mac os x 10.6.6 on final cut pro

    Hello, I am thinking to download Final Cut Pro X. However my mac book pro is a Mac OS X v10.6.6 will I be able to the program or do I have to upgrade to v10.6.8. And if I do have to upgrade where can I get the 10.6.8 version? Please reply back asap.