Path to redo logs after restoring of controlfile

Hello!
After restoring of controlfile I see distorted redo logs metadata (column v$logfile.member ) :
$OH/dbs/data/ora/MY_SID/rlog/redo1a.logIn source database redo logs placed in other directory,
also I should drop logfile members and logfile groups and then to create them again , but may be there is other way to fix this issue?
Please advise.
I'm usung 11.2.0.3
Thanks and regards,
Pavel

Hello Grirsh
Thank You.
You mean you are having some other name of redolog files than in the folder ?Yes , You are right. In database never was redo with this path.
If yes, it means they may be something else, because Oracle is just using the those files which are showing in column of member of v$logfile view.Sorry. Could I ask You please to explain this phrase, as I wrote In database never was redo with this path,
from where they appear after restoring of controlfile ?
I saw the binary file from which control file was created through browsers, it doesn't contain the path mentioned in my first post
Best regards,
Pavel

Similar Messages

  • INVALID redo log after creating a new group member

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

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

  • RMAN-03008 and ORA-07217 after restore of controlfile, 11.2.0.2

    Hi,
    try to restore backup done with 11.2.0.2
    because upgrade to 11.2.0.3 has problems with workspace manager,
    - done with DBUA - which is a other part of the story.
    OS is SLES11SP1 x86_64
    Here is what happens:
    startup nomount with minimal pfile in 11.2.0.2 environment
    restore controlfile from SBT
    channel T1: restore complete, elapsed time: 00:01:45
    output file name=+DSKGRP1/alkklefq/controlfile/control01.ctl
    output file name=+DSKGRP1/alkklefq/controlfile/control02.ctl
    then
    RMAN> ALTER DATABASE MOUNT;
    database mounted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-07217: sltln: Umgebungsvariable kann nicht ausgewertet werden.
    No other command like show all, resync catalog or what ever is working,
    always fails with RMAN-03008 and ORA-07217
    and after
    run {
    allocate channel T1 type 'SBT_TAPE' format 'b_%d_%u_%p_%c.bck';
    restore database from tag 'TAG20120730T212808';
    i got
    Speicherzugriffsfehler = segmentation fault
    Can anyone throw light on this?
    Regards
    Michael

    Hello;
    Based on the information you probably I would double check my "env" for an issue. Something set wrong or not set.
    Does the "env" work without error?
    Here's what is set on mine :
    /home/oracle:PRIMARY >env
    HOSTNAME=
    TERM=
    SHELL=
    HISTSIZE=
    NLS_LANG=
    TMPDIR=
    SSH_CLIENT=
    SSH_TTY=
    USER=oracle
    LD_LIBRARY_PATH=
    LS_COLORS=
    ORACLE_SID=
    ORACLE_BASE=
    SSH_AUTH_SOCK=
    COBBLER_SERVER=
    MAIL=
    PATH=
    INPUTRC=
    PWD=
    EDITOR=
    LANG=
    TZ=
    ORACLE_TERM=
    SSH_ASKPASS=
    SHLVL=
    HOME=
    TMP=
    LOGNAME=oracle
    SSH_CONNECTION=
    LESSOPEN=
    ORACLE_HOME=
    G_BROKEN_FILENAMES=Best Regards
    mseberg
    Edited by: mseberg on Aug 6, 2012 8:02 AM

  • Applying Archive logs after restore by RMAN

    We user RMAN for our backup. I wanted to restore the database and apply all the archive logs.
    After I use
    RMAN> Restore database ( from last night backup)
    RMAN> Recover database
    And now I want to apply all the archive logs from which were generated from last night backup say 11:00 pm till 10:00 am today morning.
    How can I apply the archive logs.
    Thanks

    I have the RMAN backup on tape , and I have the archive logs on the disk , as the archive logs would be backed up only the following night.
    i.e i want to restore a 10th night backup , and apply the logs from 10th night 11:00 pm to 10:00 am 11th morning. As the archive logs would still be on the disk , how can I apply them..
    Thanks

  • Db restore non archive mode lost redo log file..restore from controlfile tr

    i have a db 11g I had taken non archive backup but failed to take redo log files backup...
    so while i restored the db ... after formatting the machine ..the oracle instance wont start.
    I create a controlfile trace but when i run it i get errors.
    since i dont have the older log files.. how do i get around with this issue
    Thanks
    Following is the sample of control file trace ..Note i cannot create the redo log file
    since db wont be mounted at most it shall be in nonmount mode
    and below is my created controlfile ....
    CREATE CONTROLFILE REUSE DATABASE "XE" NORESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1
    'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_80L7C259_.LOG'
    SIZE 50M BLOCKSIZE 512,
    GROUP 2
    'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_80L7C375_.LOG'
    SIZE 50M BLOCKSIZE 512
    -- STANDBY LOGFILE
    DATAFILE
    'C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSTEM.DBF',
    'C:\ORACLEXE\APP\ORACLE\ORADATA\XE\UNDOTBS1.DBF',
    'C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSAUX.DBF',
    'C:\ORACLEXE\APP\ORACLE\ORADATA\XE\USERS.DBF'
    CHARACTER SET AL32UTF8
    I dont have these 2 files ..what do i do to get around this situation
    'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_80L7C259_.LOG'
    SIZE 50M BLOCKSIZE 512,
    GROUP 2
    'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_80L7C375_.LOG'
    SIZE 50M BLOCKSIZE 512
    -- STANDBY LOGFILE
    DATAFILE
    Edited by: zycoz100 on Feb 27, 2013 10:57 PM

    If you have a cold backup (database shutdown properly) without the redo logs, change this :
    CREATE CONTROLFILE REUSE DATABASE "XE" NORESETLOGS NOARCHIVELOGto
    CREATE CONTROLFILE REUSE DATABASE "XE" RESETLOGS NOARCHIVELOGYou have to change the NORESETLOGS to RESETLOGS for Oracle to recreate the online redo logs.
    Hemant K Chitale

  • Increse of redo log size

    Hi,
    Please help me to increase the redo log size.
    As i am in DB - oracle 10G and OS - Suse linux 10SP2
    SQL> SELECT * FROM v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIME
             1          1        358  157286400          2 YES INACTIVE
       2972903289 28-NOV-11
             2          1        359  157286400          2 YES INACTIVE
       2972957401 28-NOV-11
             3          1        357  157286400          2 YES INACTIVE
       2972839164 27-NOV-11
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIME
             4          1        360  157286400          2 NO  CURRENT
       2973005629 29-NOV-11
    SQL> SELECT * FROM v$logfile;
        GROUP# STATUS  TYPE
    MEMBER
    IS_
             4         ONLINE
    /oracle/JID/origlogB/log_g14m1.dbf
    NO
             4         ONLINE
    /oracle/JID/mirrlogB/log_g14m2.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
             3         ONLINE
    /oracle/JID/origlogA/log_g13m1.dbf
    NO
             3         ONLINE
    /oracle/JID/mirrlogA/log_g13m2.dbf
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    NO
             2         ONLINE
    /oracle/JID/origlogB/log_g12m1.dbf
    NO
             2         ONLINE
        GROUP# STATUS  TYPE
    MEMBER
    IS_
    /oracle/JID/mirrlogB/log_g12m2.dbf
    NO
             1         ONLINE
    /oracle/JID/origlogA/log_g11m1.dbf
    NO
        GROUP# STATUS  TYPE
    MEMBER
    IS_
             1         ONLINE
    /oracle/JID/mirrlogA/log_g11m2.dbf
    NO
    8 rows selected.
    Please help me how to execute for the above query.
    Thanks,
    Hariharan

    Hello
    Complete step:
    Step 1 SQL> select a.group#, a.member, b.bytes/1024/1024 mb from v$logfile a, v$log b where a.group# = b.group#;
    This query will show current group with redo log members and their size.
    Step 2 Make the last redo log CURRENT one
    To find which group is current at this moment use following query
    SQL> select group#, status from v$log;
    GROUP#         STATUS
    1                    CURRENT
    2                    INACTIVE
    3                    INACTIVE
    4                    INACTIVE
    Now as you can see that the first group is marked as current but we need to make group 4 as current. So force group 4 to become current one by switching log file. To switch log file use following query.
    SQL> alter system switch logfile;
    GROUP#         STATUS
    1                     INACTIVE
    2                    CURRENT
    3                    INACTIVE
    4                  INACTIVE
    SQL> alter system switch logfile;
    GROUP#        STATUS
    1                     INACTIVE
    2                     INACTIVE
    3                     INACTIVE
    4                    CURRENT
    Step 3 Drop the first online redo log
    After making the last online redo log file the CURRENT one, drop the first online redo log:
    SQL> alter database drop logfile group 1;
    Database altered.
    Note:
    Be aware that if you are going to drop a logfile group, it cannot be the current logfile group. However, where attempting to drop the logfile group resulted in the following error as a result of the logfile group having an active status:
    SQL> ALTER DATABASE DROP LOGFILE GROUP 1;
    ALTER DATABASE DROP LOGFILE GROUP 1
    ERROR at line 1:
    ORA-01624: log 1 needed for crash recovery of instance ORA920 (thread 1)
    ORA-00312: online log 1 thread 1: ''
    Easy problem to resolve. Simply perform a checkpoint on the database:
    SQL> ALTER SYSTEM CHECKPOINT GLOBAL;
    System altered.
    SQL> ALTER DATABASE DROP LOGFILE GROUP 1;
    Database altered.
    Step 4 You need to re-create dropped online redo log group with different size. Use the following query to achieve this.
    SQL> alter database add logfile group 1 ('<path>/origlogA/log_g11m1.dbf','<path>/mirrlogA/log_g11m2.dbf') size 200M reuse;
    Database altered.
    Step 5 Force another log switch
    After re-creating the online redo log group, force a log switch. The online redo log group just created should become the "CURRENT" group:
    SQL> select group#, status from v$log;
    GROUP#         STATUS
    1                     UNUSED
    2                     INACTIVE
    3                     INACTIVE
    4                    CURRENT
    SQL> alter system switch logfile;
    SQL> select group#, status from v$log;
    GROUP#         STATUS
    1                      CURRENT
    2                      INACTIVE
    3                      ACTIVE
    Step 6 # Loop back to Step 3 until all logs are rebuilt
    After re-creating an online redo log group, continue to re-create (or resize) all online redo log groups until all of them are rebuilt.
    Regards,
    Rajan

  • How can resize redo log ?

    hi, i want how can resize redo log size,
    i have try resize redo log file following way
    1] first i have my redo log size is
    GROUP# STATUS MEMBER SIZE
    3 ONLINE /oradata/xyz/redo03.log 100M
    2 ONLINE /oradata/xyz/redo02.log 100M
    1 ONLINE /oradata/xyz/redo01.log 100M
    I want this size is reducing , i have try following way
    1] first i have create GROUP 4 add member
    ALTER DATABASE ADD LOGFILE GROUP 4 ('/oradata/xyz/redo04.log') SIZE 30M;
    then
    alter system switch logfile;
    in this way i have create remaning two redo log,
    after create i have delete old redo log, is is correct method for reducing redo log.

    Check Note: 1035935.6 - Example of How To Resize the Online Redo Logfiles
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=1035935.6

  • About redo logs

    Hi! May I ask you a question... B-)
    Sybex OCA guide. page 506 8th line:
    A redo log file records all changes to the database in most cases before the changes are written to the datafiles.in wich cases rocordes are written to the redo logs after/during chanches in the datafiles? X-(
    thanks in advance. :D

    Strictly speaking both "all operations with nologging clauese" and "operations on objects which are in nologging state" are incorrect.
    You may put a NOLOGGING clause in an operation but find that it still does Logging. (eg if you put a Hint "APPEND NOLOGGING" on a Logging table, the INSERT is still logging because the "NOLOGGING" is not a valid hint and is ignored. Similarly if you put a CREATE TABLE ... AS SELECT * FROM .. NOLOGGING; also the NoLogging is ignored because it is invalid).
    Similarly, you could set a table to NOLOGGING but all regular DML will still be logging.
    Therefore, only operations that support NOLOGGING will be nologging.

  • Error after Restoring Datafiles in Archivelog but missing archive log files

    Hi all,
    I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files. Yesterday night i have restored my DB .
    I m happy to have my datafile contents till yesterday morning.
    But after restoring when i try to open th DB, i m facing the following errors:
    SQL>          Startup open;
    Oracle instance started but in mounted stagell
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL>         alter database open resetlogs;
    Error: ORA-01113: file 1 needs media recovery
              ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
    SQL>         recover database using backup controlfile until cancel;
    ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
    ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
    ORA-00280: change 266277189 for thread 1 is in sequence #3020
    ORA - 01112: media recovery not started
    SQL>   recover;
    ORA-00283: recovery session cancelled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    Alert Log File:
    Starting up ORACLE RDBMS Version: 10.2.0.2.0.
    System parameters with non-default values:
      processes                = 80
      sessions                 = 96
      event                    = 10191 trace name context forever, level 1
      sga_max_size             = 633339904
      shared_pool_size         = 301989888
      shared_pool_reserved_size= 30183260
      filesystemio_options     = setall
      control_files            = E:\ORACLE\IE6\ORIGLOGA\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\ORIGLOGB\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\SAPDATA1\CNTRL\CNTRLIE6.DBF
      control_file_record_keep_time= 30
      db_block_size            = 8192
      db_cache_size            = 301989888
      compatible               = 10.2.0
      log_archive_dest         = E:\oracle\IE6\oraarch\IE6arch
      log_buffer               = 2854912
      log_checkpoint_interval  = 0
      db_files                 = 254
      log_checkpoints_to_alert = TRUE
      dml_locks                = 4000
      undo_management          = AUTO
      undo_tablespace          = PSAPUNDO
      undo_retention           = 43200
      recyclebin               = off
      remote_os_authent        = TRUE
      remote_login_passwordfile= EXCLUSIVE
      job_queue_processes      = 1
      background_dump_dest     = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
      user_dump_dest           = E:\ORACLE\IE6\SAPTRACE\USERTRACE
      core_dump_dest           = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
      optimizer_features_enable= 10.2.0.1
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = IE6
      open_cursors             = 800
      optimpeek_user_binds   = FALSE
      pga_aggregate_target     = 402443468
      workarea_size_policy     = AUTO
      statistics_level         = typical
    PMON started with pid=2, OS id=804
    PSP0 started with pid=3, OS id=9580
    MMAN started with pid=4, OS id=5840
    DBW0 started with pid=5, OS id=8136
    LGWR started with pid=6, OS id=8712
    CKPT started with pid=7, OS id=1620
    SMON started with pid=8, OS id=7084
    RECO started with pid=9, OS id=9576
    CJQ0 started with pid=10, OS id=9156
    MMON started with pid=11, OS id=6000
    MMNL started with pid=12, OS id=2856
    Sat Apr 18 04:01:29 2009
    ALTER DATABASE   MOUNT
    Sat Apr 18 04:01:33 2009
    Setting recovery target incarnation to 1
    Sat Apr 18 04:01:33 2009
    Successful mount of redo thread 1, with mount id 1124466585
    Sat Apr 18 04:01:33 2009
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE   MOUNT
    Sat Apr 18 04:01:34 2009
    ALTER DATABASE OPEN
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Sat Apr 18 04:02:13 2009
    alter database open resetlogs
    Sat Apr 18 04:02:13 2009
    ORA-1245 signalled during: alter database open resetlogs...
    Sat Apr 18 04:11:05 2009
    ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
    Sat Apr 18 04:11:05 2009
    Media Recovery Start
    Sat Apr 18 04:11:06 2009
    Media Recovery failed with error 1610
    ORA-283 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL...
    Sat Apr 18 04:11:28 2009
    ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE
    Sat Apr 18 04:11:28 2009
    Media Recovery Start
    parallel recovery started with 3 processes
    ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE...
    Sat Apr 18 04:17:23 2009
    ALTER DATABASE RECOVER  database using backup controlfile until cancel 
    Sat Apr 18 04:17:23 2009
    Media Recovery Start
    ORA-275 signalled during: ALTER DATABASE RECOVER  database using backup controlfile until cancel  ...
    Any suggestions pls..............
    Thanks & Regards,
    Subbu

    Hello Subbu,
    > I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files.
    You mean you have taken an online backup and lost all your archive log files after that online backup?
    SQL> alter database open resetlogs;
    Error: ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
    SQL> recover database using backup controlfile until cancel;
    ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
    ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
    ORA-00280: change 266277189 for thread 1 is in sequence #3020
    To perform a recovery with an online backup you will need all archive log files until the end of the online backup. If you have lost them you are not able to recover (or open) your database in a consistent state.
    So the only suggestion we can do is:
    You need the archive log files that were created during the online backup to perform an incomplete recovery ... if they are gone you can not restore your database.
    Regards
    Stefan

  • How Do I Restore Deleted Redo Logs

    I currently have alter database archivelog set and am backing up my archive log redo file. However, I am trying to test a scenario where all of my redo log files have been deleted, and thus need to be restored. I have backups of my archivelog files. I'm trying to recover my redo log files by executing the following:
    RMAN> restore archivelog all;
    Starting restore at 14-AUG-02
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=9 devtype=DISK
    archive log thread 1 sequence 102 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00102.001
    archive log thread 1 sequence 103 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00103.001
    archive log thread 1 sequence 104 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00104.001
    restore not done; all files readonly, offline, or already restored
    Finished restore at 14-AUG-02
    Since this doesn't work I'm assuming I'm doing something wrong. Therefore, what are the necessary steps for recovering my redo log files after they have been deleted? Thanks to all for your help.

    Since my test assumes that the Control files, redo logs and all tablespaces and data files have been deleted. These are the steps I'm using to attempt a full backup & recovery.
    3.     Login to SQLPLUS sys/jalisco@bas as sysdba
    4.     SQL> startup mount bas <enter>
    5.     SQL> alter database archivelog; <enter>
    6.     Stop the Listener and Instance through Services or Net Stop as before.
    7.     From a command enter C:\Oracle\startoracle jalisco bas.
    8.     Login to RMAN: rman target sys/jalisco@bas <enter>
    9.     RMAN> configure controlfile autobackup on; <enter>
    10.     RMAN> backup database format
    a.     2> /oraclebackup/rman_%d_%t.bas plus archivelog; <enter>
    At this point Oracle is configured so that both the archivelog and control files get backed up to oracle\ora90\database. The archivelogs get stored in oracle\ora90\rdbms.
    1.     Restore the control files.
    2.     Restore the archivelogs.
    3.     Restore the tablespaces and data files.
    4.     Create new reset logs.
    1.     Confirm that the Listener and BAS service have been started through the Contol Panel, or by using Net Start.
    2.     Login to RMAN: rman target sys/jalisco@bas as sysdba
    3.     RMAN> startup nomount
    4.     RMAN> restore controlfile from /oracle/ora90/database/C-493922189-2002MMYYYY-00;
    5.     RMAN> startup mount
    6.     RMAN> run {
    a.     2> restore archivelog all; }
    7.     RMAN> restore database;
    8.     Exit RMAN and Login to SQLPLUS sys/jalisco@bas as sysdba
    9.     SQL> alter database open resetlogs;
    At this point I get the error which is listed in the above thread.
    At this point a complete recovery should have taken place. It is extremely important to create a new backup now before proceeding.

  • 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.

  • Restoring archive log after cold backup

    Hello forums users,
    I read many thing on this topic but I didn't find the good answer.
    I performed a cold backup each sunday.
    My database is in ARCHIVE LOG mode.
    Is it possible to restore ARCHIVE LOG files after restoring COLD backup?
    Sunday : cold backup
    Monday : new archive log have been created since cold backup
    Tuesday : same as Monday
    Wednesday : I would like to restore to Monday 22:00 for example
    Can I restore cold backup + apply archive log until Monday 22:00 ?
    Regards,
    Guillaume

    recover database using backup controlfile until cancel|time|logseq|scn
    will do this and prompt you for the archivelogs.
    Known as 'incomplete recovery'
    Hth
    Sybrand Bakker
    Senior Oracle DBA

  • Recover database without controlfile and redo logs

    Hi guys,
    I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
    -All controlfiles are missing
    -All redo logs are missing
    -I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
    -The database is in archivelog mode
    -The database was created with OMF (Oracle Managed Files)
    So I have done this steps:
    1) When the database was opened I rename all controlfiles and all redo logs
    2) Shutdown Abort
    3) I run the bkp_controlfile.sql, here I have a problem...
    The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1:
    '/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
    Any suggestion to help me?
    Thanks a lot.

    Excelent! Thanks for your answers Markus and Hemant.
    In conclusion...
    - If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
    - if we haven´t all redo logs availables, there are 2 situations:
    1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
    2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
    With all this I close this thread. Was very good experience.
    If anyone would add something will be welcome.
    Thanks for all
    I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
    ALL IN ONE SESSION*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    Database opened.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> @/home/oracle/bkp_controlfile.sql
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Control file created.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
    ORA-00289: suggestion :
    /u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
    ORA-00280: change 398764 for thread 1 is in sequence #40
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    Tablespace altered.
    SQL>
    ALL IN DIFERENT SESSIONS*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
    Database altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    SQL> ALTER DATABASE ARCHIVELOG;
    Database altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> SHUTDOWN IMMEDIATE
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3

  • After increasing redo log groups we are getting given alerts continvously

    earlier having 6 redo log groups with 32 MB.but 7 days back our database was hangs .no one was able to login into sqlplus except sys user ,but not able to perform any dml operation.after rebooting our 2-node RAC instances it was running fine nearly about 6-7 hrs and again hangs.we did 4-5 times and same thing happend again and again.so we had added more redo logs of 100 MB size and removed previous one.then our hangs problem resolved but continvously getting given things in alert logs for both RAC instances(9.2.0.8).our os is linux
    {color:#ff0000}Wed Dec 3 05:04:31 2008
    ARC1: Completed archiving log 15 thread 1 sequence 282036
    ARC1: Evaluating archive log 17 thread 1 sequence 282037
    ARC1: Unable to archive log 17 thread 1 sequence 282037
    Log actively being archived by another process
    ARC1: Evaluating archive log 13 thread 1 sequence 282038
    ARC1: Beginning to archive log 13 thread 1 sequence 282038
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282038.arc'
    Wed Dec 3 05:04:31 2008
    Thread 1 advanced to log sequence 282040
    Current log# 15 seq# 282040 mem# 0: /MemsRedoA/redo15_1.log
    Current log# 15 seq# 282040 mem# 1: /MemsRedoB/redo15_2.log
    Wed Dec 3 05:05:21 2008
    ARC1: Completed archiving log 13 thread 1 sequence 282038
    ARC1: Evaluating archive log 17 thread 1 sequence 282037
    {color}{color:#ff0000}*ARC1: Unable to archive log 17 thread 1 sequence 282037*
    Log actively being archived by another process
    ARC1: Evaluating archive log 18 thread 1 sequence 282039
    ARC1: Beginning to archive log 18 thread 1 sequence 282039
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282039.arc'
    Wed Dec 3 05:05:21 2008
    ARC0: Completed archiving log 17 thread 1 sequence 282037
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    {color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    {color}{color:#ff0000}*ARC0: Unable to archive log 18 thread 1 sequence 282039*
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    ARC0: Evaluating archive log 18 thread 1 sequence 282039
    ARC0: Unable to archive log 18 thread 1 sequence 282039
    Log actively being archived by another process
    Wed Dec 3 05:05:49 2008
    ARC1: Completed archiving log 18 thread 1 sequence 282039
    Wed Dec 3 09:01:02 2008
    Thread 1 advanced to log sequence 282041
    Current log# 17 seq# 282041 mem# 0: /MemsRedoA/redo17_1.log
    Current log# 17 seq# 282041 mem# 1: /MemsRedoB/redo17_2.log
    Wed Dec 3 09:01:02 2008
    ARC1: Evaluating archive log 15 thread 1 sequence 282040
    ARC1: Beginning to archive log 15 thread 1 sequence 282040
    Creating archive destination LOG_ARCHIVE_DEST_2: 'SBMEMS'
    Creating archive destination LOG_ARCHIVE_DEST_1: '/MemsArchive/0001_0000282040.arc'
    Wed Dec 3 09:01:29 2008
    ARC0: Evaluating archive log 15 thread 1 sequence 282040
    {color}{color:#ff0000}*ARC0: Unable to archive log 15 thread 1 sequence 282040*
    Log actively being archived by another process
    Wed Dec 3 09:01:37 2008
    ARC1: Completed archiving log 15 thread 1 sequence 282040
    {color}ORADB1:MEMS1:oracle$
    please suggest solution for this.
    Thanks

    As Sybrand pointed out, this msg can be ignored. It clearly states that a given arch process cannot archive a given redo because that redo is already being handled by a different arch process. If you follow your alert log a little further, you'll see that the referenced thread is eventually completed.
    I'd be curious to see the alert log from when you were locked up and only sysdba could log on. See what led you to believe that adding more redo log groups would solve your problem.

  • Corruption of archived logs after redo resizing - URGENT

    Hello all,
    We have a RAC 9i 2-node DB, running on RHEL 3 machines.
    We resized our redo logs from 100M to 1G to avoid "Can not allocate log, archival required" messages.
    The operation was successful, but now we are facing problems with the ext3 filesystem holding the archived logs.
    Each node has its own arc location, mounted only once.
    When we run "ls" in the arc destination, we get "ls: Input/output error" messages.
    RMAN complains also about corrupted arcvhived logs.
    The day before Yesterday we reformatted one arc destination, and today the messages appeared in the other one.
    Do you have any suggestion?
    Jonathan

    Did the problem occur right after increasing the log size? Then the first thing to do would be to decrease the log size, but add more log groups to fix the "Can not allocate..." problem.
    If "ls" doesn't work, your file system is stuffed.Reformat the archive dest and do simple file copies to verify the integrity, before putting the archive logs back on.
    That's just for starters...

Maybe you are looking for