How to restore cold backup + archived log files

Hi,
Suppose I take a cold backup on 18th. After that I have four days of archived log files. if the database crashes on 5th day, I have to restore the 18th cold back + 4 days of archived log files. How do I restore since it is a cold backup and I cant do incomplete recovery.
can I use
Recover database ( with 18th cold backup) in mount state and apply archived logs.
Prabhath

The details of how you perform forward recovery using a cold backup depends on
1- rman or manual backup
2- using current or backup control file
3- if rman, recovery catalog or no recovery catalog
4- if full database recovered or only a few files
Each of these conditions will affect what is known to Oracle and what needs to be done. For example if you restored the entire cold backup including the control file then Oracle would see a consistent database and not need to perform recovery so you would need to startup mount and tell the database to perform recovery using a backup control file. If using rman and no recovery catalog you might need to catalog some of the archived redo logs, etc....
It is advisable to consult the Backup and Recovery manuals before attempting recovery for any new scenario.
HTH -- Mark D Powell --

Similar Messages

  • COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

    제품 : ORACLE SERVER
    작성날짜 : 2002-04-09
    COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
    ======================================================================
    PURPOSE
    COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
    과정을 TEST로 확인하여 본다.
    Examples
    No Archive log mode.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    0
    SQL> select count(*) from emp4 ;
    COUNT(*)
    0
    Cold backup을 받은후 Archive log mode 변경한 경우
    SVRMGR> startup mount
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    SVRMGR> alter database open ; => archive log mode 변경.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> insert into emp3 select * from emp ;
    14 rows created.
    SQL> commit ;
    Commit complete.
    SQL> insert into emp4 select * from emp1 ;
    71680 rows created.
    SQL> commit ;
    Commit complete.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    ## log switch 발생.
    SVRMGR> alter system switch logfile ;
    SQL> insert into emp3 select * from emp ; -- current log에 반영.
    14 rows created.
    SQL> commit ;
    SQL> select count(*) from emp3 ;
    COUNT(*)
    28
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # ALL DATABASE CRASH #
    # recover 과정... #
    1. Restore Cold-backup
    2. modify initSID.ora
    log_archive_start = true
    log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
    log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
    3. svrmgrl
    Statement processed.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
    ORA-00280: change 340421 for thread 1 is in sequence #28
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
    ORA-00280: change 340561 for thread 1 is in sequence #29
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
    ORA-00280: change 340642 for thread 1 is in sequence #30
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
    ORA-00280: change 340723 for thread 1 is in sequence #31
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
    ORA-00280: change 340797 for thread 1 is in sequence #32
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    SVRMGR> alter database open resetlogs ;
    Statement processed.
    SVRMGR>
    SQL> connect scott/tiger
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # 결론...... #
    따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
    없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
    가능하다.
    # 주의 사항 #
    cold backup을 restore한 후 database open후 shutdown 한 다음 archive
    log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
    때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
    주의하여야 한다.
    SVRMGR> startup
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    Database opened.
    SVRMGR> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
    ORA-00280: change 339542 for thread 1 is in sequence #3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
    240], [], []
    SVRMGR> exit
    Server Manager complete.
    Rederence Documents
    ---------------------

  • How to recover a lost archive log file?

    How to recover a lost archive log file? Do I need to open the database with RESETLOGS after recovery?-------No.156

    I think he might rewrite the question in his own words.
    I guess in the event of lost archive logs during db recovery, you have to open RESETLOGS and say goodbye to some of the data.

  • How does one name an Archive Log file in ARC%S_%R.%T format

    Hallo!I have been trying to enable Archive Log mode for the Oracle 10g database.
    In OEM,I went via the links Maintenance->Recovery Settings->Media Recovery
    There,a text box by the name Log Archive Filename Format requires one to name the Archive Log file in ARC%S_%R.%T format.
    I have tried several times to name the Archive log e.g ARC001_001.001 but when I shutdown and restart the database instance,the error below appears
    ORA-19905: log_archive_format must contain %s, %t and %r.
    This error has proved impossible to rectify and I am forced to uninstall then re-install Oracle 10g.
    I would like to have back-ups in archive log mode.Please give me the best way to name the Archive Log file i.e with an example name so that I can have online back-ups.
    Thanks.

    Hi,
    If you try to change the LOG_ARCHIVE_FORMAT to something other than the default %s,%t,%r, it will fail
    Perform as the below steps in order to enable archive log mode
    SQL>create pfile from spfile
    SQL>create pfile='c:\temp\init.ora' from spfile;
    SQL>created;
    SQL>shutdown immediate;
    edit the init.ora file by adding the following information
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\db\archive1'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'
    Start the DB with modified pfile.
    - Pavan Kumar N
    Edited by: Pavan Kumar on May 2, 2010 2:17 PM

  • How to correct the corrupted archive log files?

    Friends,
    Our restore method is cloning type.
    today i fired this statement(this is one is usually do for the restore) "recover database until cancel using backup controlfile"
    i have 60 files in the archive folder.
    it executs only 50 files when it comes to 51st file it came out and says could not copy the file.
    is that particular file is corrupted?
    or is there any restriction in copying no of archivelog files? i mean only 60 files like that.....
    suppose if the archive file is corrupted how can i correct it?
    thanks
    sathyguy

    Now, this is the error message....
    ORA-00310: archived log contains sequence 17480; sequence 17481 required
    ORA-00334 archived log; '/archive2/OURDB/archive/ar0000017481.arc'i googled....and find out.....
    ORA-00310 archived log contains sequence string; sequence string required
    Cause: The archived log is out of sequence, probably because it is corrupted or
    the wrong redo log file name was specified during recovery.
    Action: Specify the correct redo log file and then retry the operation.so...from the above error messages.....i think the particular archive file(17481) is corrupted. now can i correct this corrupted archive file.
    According to the above action, it says to specify the correct redo log file. if the file is not corrupted then where should i specify the redo log file's path?
    thanks
    sathyguy

  • Scripted Cold Backups / Archived Logs / Flashback

    Facts:
    uname -a:
    SunOS {hostname omitted} 5.8 Generic_117350-39 sun4u sparc SUNW,Sun-Fire-V240
    select * from v$version:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Solaris: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    Archivelog enabled
    Flashback enabled
    db_flashback_retention_target = 7200 (5 days)
    archive_lag_target = 1800 (30 minutes)
    No, we are not using rman (yet). This system does not have a 24/7 SLA, so we run a cold backup every Saturday: a shell script shuts down the database and copies all the necessary files to a safe location on another host.
    We do have one problem: an accumulation of archived logs. I know that we don't need to keep the logs older than the latest cold backup, but I am unsure of the correct way to clean them up, especially given that we have flashback enabled. Any suggestions?
    Thanks!

    I think maybe I just found the answer to my own question.
    Upon examining the flashback_recovery_area more closely, I see an archivelog directory and a flashback directory, which contains a number of flb files going back to 12/14 (today is 12/20). This makes a certain amount of sense since we have the flashback retention target set to 5 days.
    Would I be correct in stating that the flashback files are self-managing and completely independent of the archived logs?
    Would I also be correct in stating that I can happily delete the archive logs older than my last cold backup?
    The thing which gives me pause is that I swear I remember reading somewhere that flashback uses the archived logs. Did I misunderstand something?

  • How to restore cold backups on other server

    Hi all
    On Oracle9i production server, we have windows scheduled job to take the cold backups every day night. The size of the database is 2GB.
    Now, the cold backup consists of
    - Database files & Log files
    - Parameter file
    - Control file.
    I am required to check the validity of the cold backup we have. So, I need to restore the database in another server.
    So, please provide me the steps I need to do to restore the database.
    Thanks.

    See Chapter 3 "Performing User-Managed Restore Operations" of the
    "Oracle9i User-Managed Backup and Recovery Guide Release 2 (9.2)" (Part Number A96572-01)
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96572/osrestore.htm#26029
    Best to start with Chapter 1 "Introduction ..."
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96572/intro.htm#431510
    and Chapter 2 "Making User-Managed Backups"
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96572/osbackups.htm#10000
    If you are on Windows note that besides installing the sofwtare you must also create the Oracle Service before you restore a database backp to another server.
    See Chapter 6 "Backing Up and Recovering Database Files" in the Oracle Database Administrator's Guide for Windows
    http://download.oracle.com/docs/cd/B10501_01/win.920/a95491/backup.htm#1004903

  • How to delete the standby archive log files in ASM?

    Hi Experts
    we have a realtime downstream replication that is using the a location in ASM to put the shipped logs files.
    set up by
    ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=+BOBOASM/NANPUT/standbyarchs/
    VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)' Scope=BOTH;
    What shall i do to clean up those files ?
    Any procedure or script to do that?
    Thanks

    Hello Haggylein
    check this out, seems to work
    --- redologs used or not?
    ---- when purgeable we can delete it
    COLUMN CONSUMER_NAME HEADING 'Capture|Process|Name' FORMAT A15
    COLUMN NAME HEADING 'Archived Redo Log|File Name' FORMAT A25
    COLUMN FIRST_SCN HEADING 'First SCN' FORMAT 99999999999
    COLUMN NEXT_SCN HEADING 'Next SCN' FORMAT 99999999999
    COLUMN PURGEABLE HEADING 'Purgeable?' FORMAT A10
    SELECT r.CONSUMER_NAME,
    r.NAME,
    r.FIRST_SCN,
    r.NEXT_SCN,
    r.PURGEABLE
    FROM DBA_REGISTERED_ARCHIVED_LOG r, DBA_CAPTURE c
    WHERE r.CONSUMER_NAME = c.CAPTURE_NAME and PURGEABLE = 'YES';
    -- Now the script
    -- to be executed on the downstream database
    -- generate the list of logs to be purged and executed in a ksh script
    -- sqlplus "/as sysdba" @$HOME/bin/generate_list.sql
    SET NEWPAGE 0
    SET SPACE 0
    SET LINESIZE 150
    SET PAGESIZE 0
    SET TERMOUT OFF
    SET ECHO OFF
    SET FEEDBACK OFF
    SET HEADING OFF
    SET MARKUP HTML OFF SPOOL OFF
    spool list_purgeable_arch_redologs.ksh
    SELECT 'asmcmd ls ' || r.NAME
    FROM DBA_REGISTERED_ARCHIVED_LOG r, DBA_CAPTURE c
    WHERE r.CONSUMER_NAME = c.CAPTURE_NAME and PURGEABLE = 'YES';
    spool off
    exit
    # eventually we can call it from a script
    # !ksh
    # delete of the shipped redologs
    # to be performed on node 2
    # not to be used on
    $HOME/bin/export ORACLE_SID=+ASM2
    ./list_purgeable_arch_redologs.ksh
    exit

  • Archived Log files

    Hello,
    I have a understanding problem off the function of the archived log files. My Oracle 9i Database is running in ARCHIVELOG. So if the online log files are full they get backed up to 3 different locations.
    However if I view now the v$archive_log view then I see all the archived log files.
    So now my questions:
    1. At which point does these archived log files get deleted ?
    2. If they never get deleted how do I know which archived log file can I delete.
    3. If I run a full hot/cold backup can I delete this archive log files?
    4. Is there any other way to delete the archived log files then using rman "delete input" option ? Like is there any way to delete the archived log files form the sqplplus prompt ?
    I have searched and read some articles in the net about it but it is always just about how to set up the db into archivelog mode but I was not able to find anything answering my questions.
    Thank you
    Marcus

    Out of the box, archived logs are not deleted
    automatically. However, you can delete them via
    RMAN. RMAN will delete them based on the set
    retention policy. You can see which logs and
    backups RMAN considers obsolete via the "report
    obsolete" command. RMAN keeps track of logs that
    are necessary for recovery, and those that can
    be safely deleted.
    Another option, as you have noted, is to backup
    archivelogs using RMAN, with the "delete input"
    option.
    The best option (IMHO) is to automate deletion
    of obsolete archive logs via a script. This
    can be done using the "delete noprompt obsolete"
    RMAN command.
    I'm not aware of any SQLPlus based method to delete
    logs. In any case, this would NOT be a good idea, as
    RMAN would not be aware of any such deletions.
    Hope this helps.
    Kailash.

  • Backup archive logs problem using RMAN

    Hi guys
    I got failure when using RMAN to backup archive log files:
    Starting backup at 20-APR-06
    current log archived
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 04/20/2006 21:53:57
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/o1_mf_1_1_21p5c251_.arc
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    RMAN> **end-of-file**
    My archive log files location:
    SQL> show parameter log_archive_dest
    NAME TYPE VALUE
    log_archive_dest_1 string LOCATION=/opt/oracle/oradata/DB10G/arch/
    Current archive log files:
    $ ls /opt/oracle/oradata/DB10G/arch
    1_17_586191737.dbf 1_21_586191737.dbf 1_25_586191737.dbf 1_29_586191737.dbf 1_33_586191737.dbf
    1_18_586191737.dbf 1_22_586191737.dbf 1_26_586191737.dbf 1_30_586191737.dbf 1_34_586191737.dbf
    1_19_586191737.dbf 1_23_586191737.dbf 1_27_586191737.dbf 1_31_586191737.dbf 1_35_586191737.dbf
    1_20_586191737.dbf 1_24_586191737.dbf 1_28_586191737.dbf 1_32_586191737.dbf afiedt.buf
    $
    But when I check v$archived_log:
    SQL> select name,status,deleted from v$archived_log;
    NAME S DEL
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/ A NO
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_18/ A NO
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_19/ A NO
    /opt/oracle/oradata/DB10G/redo01.log A NO
    /opt/oracle/oradata/DB10G/redo02.log A NO
    /opt/oracle/oradata/DB10G/redo03.log A NO
    /opt/oracle/oradata/DB10G/arch/1_5_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_6_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_7_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_1_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_2_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_3_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_4_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_5_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_6_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_7_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_8_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_9_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_10_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_11_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_12_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_13_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_14_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_15_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_16_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_17_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_18_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_19_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_20_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_21_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_22_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_23_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_24_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_25_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_26_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_27_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_28_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_29_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_30_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_31_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_32_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_33_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_34_586191737.dbf A NO
    More records than actual archived logs. How could it happen? How to solve?
    THanks in advance.
    Sharon

    Hi,
    Use
    RMAN>crosscheck archivelog all; cmd

  • How to Recover database from old backup and full archive log file

    Hi Oracle expert!
    I met problem when restore my oracle database.
    In my case:
    - My database version: 10.2.0.2
    - I have a database full backup (01-Nov)
    - I have all Archived log file from (01-Nov -> 05-Nov)
    - My database drop in 05-Nov with disk error (no datafile, no redo..).
    - I have no any RMAN backup from (01-Nov -> 05-Nov)
    How can i restore my database to 05-Nov?
    Thanks

    user10280724 wrote:
    Hi Chinar.
    When i used RMAN flow as your step, but i met the problem!
    - After recover database i select sequence#, applied from v$archived_log;
    --> it apply newest archived log that i had.
    - but when I select Data from table created between 01-Nov to 05-Nov, it not found!
    Not the same way the step:
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL?
    It apply newest the same archived log i had table created between 01-Nov to 05-Nov.
    How can i do with RMAN to recover my table?That is not possible,if your all available archive logs applied using rman or through sqlplus(recover database using backup controlfile until cancel) and one of these logs contain your table then there are not any problems.So there are not any difference between recovery using rman and user managed(using sqlplus),but there main matter is applying all archive logs.So first check through rman list copy of archivelog all or list backup of archivelog all and identify there in rman repository is any information or not about these logs.

  • How to recover the database when some of the archive log file get deleted.

    I am facing a problem with Oracle database, which is related to archivelogs.
    Our development database is running in archivelog mode, but we don't have backups scheduled and have no recovery catalog.
    When the database was in running condition, disk got full, so some archivelogs were deleted manually.
    After this they restarted the DB, and now DB is not coming up. Errors are as follows:
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1444383504 bytes
    Fixed Size 731920 bytes
    Variable Size 486539264 bytes
    Database Buffers 956301312 bytes
    Redo Buffers 811008 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    SQL> recover datafile '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    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 215548705 generated at 09/02/2008 17:06:10 needed for thread
    1
    ORA-00289: suggestion :
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00280: change 215548705 for thread 1 is in sequence #1107
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00308: cannot open archived log
    '/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL>
    1. How to recover the database and bring it online
    Any help will be highly appreciated.
    With Regards
    Hemant Joshi
    Edited by: hem_Kec on Sep 7, 2008 9:07 AM

    Hi,
    Archive log files are the copies of redolog files.As redo log files are circularly overwritten,oracle generates archive log file of the corresponding redo logfiles being overwritten.So if you have a backup that dates back to 10 am in the morning and if your database creashed at 3 pm,you cannot use the redo log files alone as they have incomplete information.To completely recover the database upto 3 pm,you need archive log files generated between 10 am to 3 pm. In your case since you are missing one archive log file,you cannot perform complete recovery and hence would suffer data loss.

  • 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 to remove archive log files from ASM managed 11g R2 database?

    Hi,
    I am planning to automate deletion of older archive log files from my 11g R2 Production instance which is ASM managed.
    Also want to remove the archive log files files from standby database.
    Please provide your inputs on how can I remove the older archive log files.
    Regards,
    Avinash

    Greetings
    Did you check RMAN,
    RMAN>show all;
    CONFIGURE RETENTION POLICY . . . .
    CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
    DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
    DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-10';
    This will be part of your RMAN Backup scripts/process
    Check the urls below:
    11gRel2:
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV90079
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89634
    10g:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm#sthref45
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008093
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint003.htm#sthref712
    Regards & Thanks
    BN

  • How to remove archive log files using Enterprise Manger

    Hi,
    I took backup of the archive log files and i deleted those files at OS level but it is not reflecting in the Enterprise Manager it is showing the same. Can any one help in how to delete the archive log files by using Enterprise Manger.
    version 10.2.0.1.0
    any help is appreciated.
    Regards,
    Ashraf

    I have the same problem. I have 10gr1 and 10gr2 on different servers. On 10gr1, under administration/manage current backup/image, I can see archivelog files, and can mange them. But on 10gr2, the image doesn't show archivelog files. I can only remove them using rman. I wonder if it's because the different design on 10gr2 or I missed something when setup the backup?

Maybe you are looking for