Recovery question using archive log

HPUX 11X
Oracle 10.2.0.2
I have a standby database that the customers want to test the ability to fail over. They also want to test the data integrity of the standby once it's brought on line as the primary.
I've already told the customer that any writes that they do on the standby during the test time WILL be lost. I plan on doing a incomplete recovery back to a specific sequence number / archive log when the tests are complete.
My plan is to take note of the current sequence number just before I bring the standby live. When all is said and done, I was going to do a recover back to the sequence number one PRIOR to that one. Then when I place the db back in standby mode, it will sync back up to the primary.
What I need to know is if this is a good or a bad idea. Should I plan on doing it differently and for what reason.
Thanks! :)

Use flashback database to recover the former primary database to a new standby.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
Therefore the changes made on standby won't be lost (unless you want to lose them).
If your databases do not have Flashback Database feature enabled, you can use incomplete recovery instead.
I think Flashback Database should be your first option.

Similar Messages

  • Sync database using archive log files

    Hi,
    I am having two databases A nd B. A is the live Database. I need to replicate the A database and its name as B. I had done the replication using hotbackup.
    1. create the B database
    2. then take the hotbackup and copy the files to the B database
    3. Then delete the controlfile, logfiles and datafiles then paste the files from A database.
    4. Recreate the control files in B database
    5. Now the B database is up and running.
    But my question is in A database is still live and its generating archive log files. I would like to know how to sync the B Database similar to A database using archive log files.
    Kindly share me an example..
    Rgds..

    As you have renamed and opened the clone database, it is no longer the same DBID / Database Incarnation as the source. As you point out, it is not a standby database.
    You cannot apply archivelogs from the source database to this clone.
    You have to consider [Oracle Streams|http://download.oracle.com/docs/cd/B19306_01/server.102/b14229/toc.htm] to implement data replication.
    Hemant K Chitale
    Edited by: Hemant K Chitale on Jan 5, 2010 3:34 PM

  • RMAN-06054: media recovery requesting unknown archived log

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

    In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
    Edited by: user11989003 on May 29, 2013 10:17 AM

  • Question about Archive Log Deletion policy

    I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
    Messages of the database are in German, but I guess you'll understand them.
    SQL> startup
    ORACLE-Instance hochgefahren.
    Total System Global Area 5344731136 bytes
    Fixed Size                  2129240 bytes
    Variable Size            2684355240 bytes
    Database Buffers         2617245696 bytes
    Redo Buffers               41000960 bytes
    Datenbank mounted.
    Datenbank geöffnet.
    SQL> archive log list
    Datenbank-Log-Modus              Archive-Modus
    Automatische Archivierung             Aktiviert
    Archivierungsziel            E:\oracle\thetis_iv\arch
    Älteste Online-Log-Sequenz     17917
    Nächste zu archivierende Log-Sequenz   17919
    Aktuelle Log-Sequenz           17919
    SQL> alter system switch logfile;
    System wurde geändert.I created a brand new archive log.
    SQL> exit
    Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
    D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:04    <DIR>          .
    06.04.2011  15:04    <DIR>          ..
    06.04.2011  15:04        17.137.152 ARC17919_0721667907.001
                   1 Datei(en),     17.137.152 Bytes
                   2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
    D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
    Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
    Kennwort für Recovery-Katalog-Datenbank:
    Verbindung mit Datenbank des Recovery-Katalogs
    RMAN> show all;
    RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
    Now I backup all archive logs, that havn't been backed up for at least two times.
    RMAN> run { backup archivelog all not backed up 2 times
    2>       format '%d_AR_%Y%M%D_%s_%t'
    3>       tag 'ARCHIVE LOGS'
    4>       DELETE ALL INPUT;
    5>     }
    Starten backup um 06.04.2011 15:08:01
    Aktuelles Log archiviert
    Zugewiesener Kanal: ORA_SBT_TAPE_1
    Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
    Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
    Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
    Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
    Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
    Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
    Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
    Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
    Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
    Beendet backup um 06.04.2011 15:08:10
    RMAN> exit
    Recovery Manager abgeschlossen.
    D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:08    <DIR>          .
    06.04.2011  15:08    <DIR>          ..
                   0 Datei(en),              0 Bytes
                   2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
    Thats not what I expected. Where is my mistake?

    Hi,
    I do new tests it's very strange.
    BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
    You can open a SR on MOS. (to check bugs)
    I reproduce the same test and the result was the same, it seems that this is a bug.
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
    RMAN> backup archivelog all not backed up 2 times delete all input;
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
    input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
    input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
    input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
    Finished backup at 06-APR-11
    RMAN> list archivelog all;
    specification does not match any archived log in the repositoryOracle Docs Says:
    The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
    This command eliminates the separate step of manually deleting archived redo logs.
    With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
    With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
    As explained in "Configuring an Archived Redo Log Deletion Policy",
    the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
    for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
    up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
    But in ours case it's not honors this policy.
    Only with the FORCE command should this happen. But it is not our case.
    Oracle Docs:
    If FORCE is not specified on the deletion commands,
    then these deletion commands obey the archived log deletion policy.
    If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
    Alternatively you can do the following:
    Set the commands separately.
    Check this:
    RMAN>  run {
    2> backup archivelog all not backed up 2 times ;
    3> delete archivelog all backed up 2 times to disk;
    4> }
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
    input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 06-APR-11
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
    RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

  • Recovery/db copy + archive logs

    Hi champions,
    There is one confusion in recovery of a database. Version 10g.
    I have a hot backup (using copy command) of a database(archive log mode) which I’ve taken at 22.00.00 on Sunday.
    Now my database is up and running Monday,Tuesday,Wednesday in archive log mode.I have all the archive logs since the last backup(Sunday 22.00) .and my database got crashed on Wednesday 14.00 completely lost everything (CDR files) only archive logs are with me...
    Can i recover my database using Sunday’s backup + archive log till the time it crashed.
    Regards,
    Shitesh Shukla

    Shukla Shitesh wrote:
    Hi champions,
    There is one confusion in recovery of a database. Version 10g.
    I have a hot backup (using copy command) of a database(archive log mode) which I’ve taken at 22.00.00 on Sunday.
    Now my database is up and running Monday,Tuesday,Wednesday in archive log mode.I have all the archive logs since the last backup(Sunday 22.00) .and my database got crashed on Wednesday 14.00 completely lost everything (CDR files) only archive logs are with me...
    Can i recover my database using Sunday’s backup + archive log till the time it crashed.
    Regards,
    Shitesh ShuklaDear Shitesh, you can recover the database by applying all/any archived redo log files you have.
    My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

  • Question about archived logs

    Hi!
    I wonder if there is possibility to configure archiving policy in a way:
    set one destination (/arch1/oracle) as primary, and another (/arch2/oracle) as optionally.
    redo Logs will be copied to /arch2/oracle only if /arch1/oracle fails, but after it will be available again, files will be moved (or copied) from /arch2/oracle to /arch1/oracle. Anybody tried to store backup files in that way? is it possible? I tried various combinations of log_archive_dest_n and log_archive_dest_state_n parameters, but it won't work in a way I expected.
    Message was edited by:
    wojaczek

    it's about limitation of disk place on server where DB operates. Archived logs are stored on NFS filesystem, but time to time there are some problems with remote filesystem. In such cases DB will hang and manual change of arch log destination to local FS is needed. But this destination could not be set permanently because of disk space limitations.
    When i set destination 1 as mandatory and 2 as optionally db hangs when arc can't use mandatory destination.
    Setting both destinations as optionally gives finally inconsistency and storing files on local fs, what is not desirable

  • Real - Time Apply some times uses Archived log file

    Hi All,
    I have a doubt on real time apply in Oracle 10g 10.2.0.4 version where arch process has been configured on primary database and standby has been configured for maximum performance mode with real time apply.
    But in standby alert log file i use to find below message rarely
    Media Recovery Log /oraclearch/oraarch/ctdr/5548.dbf
    Media Recovery Log /oraclearch/oraarch/ctdr/5549.dbfSo my doubt is why archived files are applied as standby has been configured for real time apply where it should apply only from standby online redo log files.
    Also i dont find any information on standby database in the view v$standby_log that these standby online log files have been archived in archived column, so how to find how much of data has been written by rfs process on SRL's...
    -Yasser

    hi,
    As the remote file server (RFS) process writes the redo data to standby redo log files on the standby database, log apply services can recover redo from standby redo log files as they are being filled.
    please check http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm
    thanks,
    baskar.l

  • When occurs crash recovery,why use active online redo log not archived log?

    If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
    Quote:
    Re: v$log : How redo log file can have a status ACTIVE and be already archived?
    Hemant K Chitale
    If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
    TanelPoder
    Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

    Aman.... wrote:
    John,
    Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
    Regards
    Aman....
    That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
    Sorry I wasted your time, I'll try to be less ambiguous in future

  • Incomplete Recovery Fails using Full hot backup & Archive logs !!

    Hello DBA's !!
    I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
    1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
    2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
    3) Restored all Hot backup files from Tape to Test Server.
    4) Restored all archive logs from tape to Test server.
    5) Restored Latest Binary Control file from Tape to Test Server.
    6) Now, Started recovery using following command from SQL prompt.
    SQL> recover database until cancel using backup controlfile;
    7) Open database after Recovery Completion using RESETLOGS option.
    Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
    ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
    1
    ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
    ORA-00280: change 7001816252 for thread 1 is in sequence #9624
    ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
    for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
    SQL> SQL> SQL> SQL> SQL> SQL> SQL>
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
    Let me know What should be the reason behind recovery failure !
    Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
    Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
    Atul Patil.

    oh you made up a new thread so here again:
    there is nothing wrong.
    You restored your backup, archives etc.
    you started your recovery and oracle applyed all archives but the archive
    '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    does not exist because it represents your current online redo log file and that is not present.
    the recovery process cancels by itself.
    the solution is:
    restart your recovery process with:
    recover database until cancel using backup controlfile
    and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    type cancel!
    now you should be able to open your database with open resetlogs.

  • Data Warehouse Archive logging questions

    Hi all,
    I'd like some opinions/advice on archive logging and OWB 10.2 with a 10.2 database.
    Do you use archive logging on your non-production OWB instances? I have a development system that only has "on demand" backups done and the archive logs fill frequently. In this scenario, should I disable archive logging? I realize that this limits my recovery options to cold backups but on a development environment, this seems sufficient for me. Would I be messing up any OWB features by turning off archive logging?
    For production instances, how large do you make your archive log (as a percentage of your total DW size perhaps)?
    How do you manage them? With Flash recovery areas? Manually? RMAN or other tools?
    Thanks in Advance,
    Mike

    Usualy, I don't set any DW tables to log. Since it's a data warehouse, I believe it's better to make cold backups. In some cases, ETL Mappings may work like backup procedures themselves.
    In OWB, select the object you need (table or index) to create. Right-click it, select Configuration -> Performance Parameters -> Logging Mode -> NOLOGGING
    Flash RecoveryDon't think it's going to help you, since most of your data manipulation is based on batch jobs.
    RMANIf you want to make hot backups, this is something that can really help you manage backup procedures.
    ManuallyMaybe... Why not?
    I don't take hot backups from DW databases. I prefer to take cold backups. In a recovery scenario, you restore the cold backup and if it's 3 days late, I execute the ETL mappings for the last 3 days.
    Regards,
    Marcos

  • Is it possible to use Archive Redo log file

    Hi friends,
    My database is runing in archive log mode.I had taken cold backup on Sunday but i am taking archive log file daily evening.
    Wednesday my database crash that means i lost all control file,redo log file,datafile etc.
    I have archived log file backup till Tuesday Night and other files like control file,datafile etc of Sunday .
    1)Is it possible to recover database till tuesday if yes HOW to use archive log file.
    (See SCN no of control file and datafiles is same ,if we use RECOVER DATABASE command oracle shows that media recovery is not requide.)
    we don't have current control file we had lost in media crash.
    null

    Dear friend
    In this scenario
    you lost the contorl file
    1>If you have old copy of Contorl file,
    which has the current structure of the
    database and all the archive files then
    you can recover the database with
    Ponint in time recovery (Using Backup Controlfile)
    suresh

  • Backup with Exp,  Can  It used in DB with Archive Log Mode ??

    I need information about if When I activate Archive log mode in my database ,after This I will use all before backups with Exp in full,Table,user ...recovery mode .
    any advice are welcome
    thanks
    Jimmy

    If you are using archive log mode, you should back up your database by regularly backing up
    your data files. If you lose a tablespace due to a defecitve disk or need to do a point-in-time recovery due to a user error, you restore your latest copy (if doing point-in-time the latest copy before the
    user error) of the relevant data files an then roll forward using the archived log.
    You can not restore your database from an export and then roll forward using the archived
    logs.
    HTH
    Marcus Geselle

  • Are archived logs useful for crashed instance?

    when the machine powers off,and start it again,the database will experience instance recover,will this kind of recover use archived log£¿I see if the database worked under unarchive mod before,then instance recover will not use archived log(no archived log).

    surpose that oracle makes a commit,and the commited
    data are already written into log file,but are not
    written back to datafile,and if the log file is
    archived,at this time OS crash.when oracle startup again
    it will user the online redo,and some of the latest
    archvied log to recover the committed data.and if the
    archvied log accidentally lost,how can oracle recovery.
    Or oracle will not reuse the online redo log until
    its data are written back to the datafile under archived
    log mod?

  • Help Educate Me on an RMAN Recovery Question

    Perhaps I am not understanding how recovery should work, so, let me lay out my situation:
    First things first:
    Oracle 11.2.0.2.5 on AIX 6.1
    Source database: POR02P on a 4 node cluster
    Auxiliary database: POR02x (single instance)
    I want to duplicate my source database to my auxiliary database as of 02-APR-2013 at 3:00PM
    Here are how my backups run:
    LEVEL0 On Sunday at 8:00 AM
    LEVEL1 Differential all other days at 8:00 AM
    Intermediate Archivelogs backups run at the following times daily: 00:45, 11:45, 19:45
    March 31 is my LEVEL0.
    So, the way I understand things, to do this duplicate:
    I need my LEVEL0 from Sunday
    I need my LEVEL1 from Monday
    I need my LEVEL1 from Tuesday
    I need all my archivelogs from just before the LEVEL1 on Tuesday started all the way to after 3:00PM on Tuesday:
    Restore archive backups from:
    4/2 11:45
    4/2 19:45
    All my backups include a controlfile.
    According to my above analysis, I made sure the required files were on disk.
    After making sure my files were on disk, I went to my source database and ran the following to make sure Oracle had all the files it needs:
    RMAN> run {
    2> set until time = "to_date('02-APR-2013 15:00:00','DD-MON-YYYY HH24:MI:SS')";
    3> restore database preview summary;
    4> }
    This above command succeeds and I can verify all the files it mentions are on disk.
    Here is the problem, the restore of the LEVEL0 and LEVEL1's succeed.  When it starts recovery, it fails asking for an archive log that both:
    *1. Was not listed as part of the PREVIEW command*
    *2. Is from a time between my LEVEL0 and first LEVEL1.*
    I was under the impression that RMAN does not need archivelogs from BETWEEN incremental backups.
    Am I wrong about this?
    Doesn't an incremental LEVEL1 differential go back to the last incremental and get all the needed blocks thereby making the "in between" archivelogs obsolete?
    If I am wrong about this, that solves part of my confusion...
    The other part of my confusion is why does the PREVIEW command not specify the archivelogs it asks for during recovery?
    If you can answer my question now, you can skip the rest.
    Else, here are all the dirty details.
    Here is mt PREVIEW command as run on the source database. The output supports how I think this should work:
    RMAN> run {
    2> set until time = "to_date('02-APR-2013 15:00:00','DD-MON-YYYY HH24:MI:SS')";
    3> restore database preview;
    4> }
    executing command: SET until clause
    Starting restore at 23-APR-2013 13:47:30
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11386312 Incr 0 105.12M DISK 00:00:23 31-MAR-2013 08:00:29
    BP Key: 11386324 Status: AVAILABLE Compressed: YES Tag: LEVEL0
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
    List of Datafiles in backup set 11386312
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
    3 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
    4 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
    5 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
    6 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
    9 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
    14 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11613131 Incr 1 122.93M DISK 00:00:21 01-APR-2013 08:00:19
    BP Key: 11613143 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f2o5vig5_1_1.BAK
    List of Datafiles in backup set 11613131
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
    3 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
    4 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
    5 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
    6 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
    9 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
    14 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11784495 Incr 1 119.81M DISK 00:00:20 02-APR-2013 08:00:19
    BP Key: 11784507 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK
    List of Datafiles in backup set 11784495
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
    3 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
    4 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
    5 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
    6 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
    9 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
    14 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11386314 Incr 0 901.41M DISK 00:03:33 31-MAR-2013 08:03:38
    BP Key: 11386326 Status: AVAILABLE Compressed: YES Tag: LEVEL0
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
    List of Datafiles in backup set 11386314
    File LV Type Ckp SCN Ckp Time Name
    2 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
    7 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
    8 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
    10 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
    11 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
    12 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
    13 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11613133 Incr 1 77.77M DISK 00:00:36 01-APR-2013 08:00:41
    BP Key: 11613145 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f1o5vig5_1_1.BAK
    List of Datafiles in backup set 11613133
    File LV Type Ckp SCN Ckp Time Name
    2 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
    7 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
    8 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
    10 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
    11 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
    12 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
    13 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11784497 Incr 1 71.67M DISK 00:00:27 02-APR-2013 08:00:32
    BP Key: 11784509 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
    List of Datafiles in backup set 11784497
    File LV Type Ckp SCN Ckp Time Name
    2 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
    7 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
    8 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
    10 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
    11 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
    12 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
    13 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    11784501 60.89M DISK 00:00:09 02-APR-2013 08:00:53
    BP Key: 11784513 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g1o626tc_1_1.BAK
    List of Archived Logs in backup set 11784501
    Thrd Seq Low SCN Low Time Next SCN Next Time
    2 147 17279219 02-APR-2013 00:45:13 17549976 02-APR-2013 08:00:35
    4 149 17279360 02-APR-2013 00:45:13 17549980 02-APR-2013 08:00:35
    1 179 17279579 02-APR-2013 00:45:15 17549968 02-APR-2013 08:00:34
    BS Key Size Device Type Elapsed Time Completion Time
    11784499 26.99M DISK 00:00:04 02-APR-2013 08:00:48
    BP Key: 11784511 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g2o626tc_1_1.BAK
    List of Archived Logs in backup set 11784499
    Thrd Seq Low SCN Low Time Next SCN Next Time
    3 149 17279600 02-APR-2013 00:45:15 17549971 02-APR-2013 08:00:34
    1 180 17549968 02-APR-2013 08:00:34 17549996 02-APR-2013 08:00:40
    3 150 17549971 02-APR-2013 08:00:34 17549999 02-APR-2013 08:00:40
    2 148 17549976 02-APR-2013 08:00:35 17550003 02-APR-2013 08:00:41
    BS Key Size Device Type Elapsed Time Completion Time
    11784500 2.00K DISK 00:00:01 02-APR-2013 08:00:52
    BP Key: 11784512 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g3o626tj_1_1.BAK
    List of Archived Logs in backup set 11784500
    Thrd Seq Low SCN Low Time Next SCN Next Time
    4 150 17549980 02-APR-2013 08:00:35 17550007 02-APR-2013 08:00:41
    BS Key Size Device Type Elapsed Time Completion Time
    11798434 28.77M DISK 00:00:05 02-APR-2013 11:45:28
    BP Key: 11798442 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g7o62k2j_1_1.BAK
    List of Archived Logs in backup set 11798434
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 181 17549996 02-APR-2013 08:00:40 17687415 02-APR-2013 11:45:05
    3 151 17549999 02-APR-2013 08:00:40 17687418 02-APR-2013 11:45:05
    BS Key Size Device Type Elapsed Time Completion Time
    11798432 20.40M DISK 00:00:03 02-APR-2013 11:45:27
    BP Key: 11798440 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g8o62k2k_1_1.BAK
    List of Archived Logs in backup set 11798432
    Thrd Seq Low SCN Low Time Next SCN Next Time
    2 149 17550003 02-APR-2013 08:00:41 17687399 02-APR-2013 11:45:03
    4 151 17550007 02-APR-2013 08:00:41 17687403 02-APR-2013 11:45:03
    2 150 17687399 02-APR-2013 11:45:03 17688884 02-APR-2013 11:45:15
    4 152 17687403 02-APR-2013 11:45:03 17688895 02-APR-2013 11:45:15
    BS Key Size Device Type Elapsed Time Completion Time
    11798433 66.00K DISK 00:00:00 02-APR-2013 11:45:27
    BP Key: 11798441 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g9o62k2n_1_1.BAK
    List of Archived Logs in backup set 11798433
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 182 17687415 02-APR-2013 11:45:05 17688871 02-APR-2013 11:45:14
    3 152 17687418 02-APR-2013 11:45:05 17688875 02-APR-2013 11:45:14
    BS Key Size Device Type Elapsed Time Completion Time
    11834701 54.22M DISK 00:00:08 02-APR-2013 19:45:32
    BP Key: 11834709 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_gdo63g6k_1_1.BAK
    List of Archived Logs in backup set 11834701
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 183 17688871 02-APR-2013 11:45:14 17982647 02-APR-2013 19:45:04
    3 153 17688875 02-APR-2013 11:45:14 17982641 02-APR-2013 19:45:04
    BS Key Size Device Type Elapsed Time Completion Time
    11834699 44.18M DISK 00:00:07 02-APR-2013 19:45:31
    BP Key: 11834707 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_geo63g6k_1_1.BAK
    List of Archived Logs in backup set 11834699
    Thrd Seq Low SCN Low Time Next SCN Next Time
    2 151 17688884 02-APR-2013 11:45:15 17982650 02-APR-2013 19:45:04
    4 153 17688895 02-APR-2013 11:45:15 17982653 02-APR-2013 19:45:04
    Media recovery start SCN is 17547912
    Recovery must be done beyond SCN 17548424 to clear datafile fuzziness
    Finished restore at 23-APR-2013 13:47:32
    Here is a summary of the files it lists:
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f2o5vig5_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f1o5vig5_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g1o626tc_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g2o626tc_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g3o626tj_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g7o62k2j_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g8o62k2k_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g9o62k2n_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_gdo63g6k_1_1.BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_geo63g6k_1_1.BAK
    Here is my list of files on disk. There are actually
    more files listed here because the PREVIEW command does
    not show pieces with Control/SPFILE backups:
    -rw-r----- 1 oracle oinstall 945201152 Mar 31 08:03 POR02P_20130331_e5o5su45_1_1.BAK
    -rw-r----- 1 oracle oinstall 110231552 Mar 31 08:00 POR02P_20130331_e6o5su46_1_1.BAK
    -rw-r----- 1 oracle oinstall 1261568 Mar 31 08:00 POR02P_20130331_e7o5su4v_1_1.BAK
    -rw-r----- 1 oracle oinstall 81559552 Apr 1 08:00 POR02P_20130401_f1o5vig5_1_1.BAK
    -rw-r----- 1 oracle oinstall 128909312 Apr 1 08:00 POR02P_20130401_f2o5vig5_1_1.BAK
    -rw-r----- 1 oracle oinstall 1277952 Apr 1 08:00 POR02P_20130401_f3o5vigv_1_1.BAK
    -rw-r----- 1 oracle oinstall 75161600 Apr 2 08:00 POR02P_20130402_fto626s5_1_1.BAK
    -rw-r----- 1 oracle oinstall 125640704 Apr 2 08:00 POR02P_20130402_fuo626s5_1_1.BAK
    -rw-r----- 1 oracle oinstall 1294336 Apr 2 08:00 POR02P_20130402_fvo626su_1_1.BAK
    -rw-r----- 1 oracle oinstall 63847936 Apr 2 08:00 POR02P_20130402_g1o626tc_1_1.BAK
    -rw-r----- 1 oracle oinstall 28300800 Apr 2 08:00 POR02P_20130402_g2o626tc_1_1.BAK
    -rw-r----- 1 oracle oinstall 2560 Apr 2 08:00 POR02P_20130402_g3o626tj_1_1.BAK
    -rw-r----- 1 oracle oinstall 30164480 Apr 2 11:45 POR02P_20130402_g7o62k2j_1_1.BAK
    -rw-r----- 1 oracle oinstall 21393920 Apr 2 11:45 POR02P_20130402_g8o62k2k_1_1.BAK
    -rw-r----- 1 oracle oinstall 68096 Apr 2 11:45 POR02P_20130402_g9o62k2n_1_1.BAK
    -rw-r----- 1 oracle oinstall 56855552 Apr 2 19:45 POR02P_20130402_gdo63g6k_1_1.BAK
    -rw-r----- 1 oracle oinstall 46324224 Apr 2 19:45 POR02P_20130402_geo63g6k_1_1.BAK
    -rw-r----- 1 oracle oinstall 3072 Apr 2 19:45 POR02P_20130402_gfo63g6r_1_1.BAK
    Okay, so at this point, I think I have everything I need.
    Here is my RMAN command:
    # start up auxiliary in nomount
    run {
    allocate auxiliary channel a1 type disk;
    allocate auxiliary channel a2 type disk;
    allocate auxiliary channel a3 type disk;
    allocate auxiliary channel a4 type disk;
    set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
    DUPLICATE DATABASE TO por02x
    BACKUP LOCATION '/backup_rman/backupset/por02p'
    NOFILENAMECHECK
    LOGFILE
    GROUP 1 ('+DB_REDO') SIZE 512M,
    GROUP 2 ('+DB_REDO') SIZE 512M,
    GROUP 3 ('+DB_REDO') SIZE 512M,
    GROUP 4 ('+DB_REDO') SIZE 512M,
    GROUP 5 ('+DB_REDO') SIZE 512M,
    GROUP 6 ('+DB_REDO') SIZE 512M,
    GROUP 7 ('+DB_REDO') SIZE 512M,
    GROUP 8 ('+DB_REDO') SIZE 512M;
    For now, I won't paste in the entire output of the log,
    just enough to see that it works fine through the restore,
    then fails at an archivelog. If someone wants the whole
    thing, I can add it in:
    RMAN> run {
    2> allocate auxiliary channel a1 type disk;
    3> allocate auxiliary channel a2 type disk;
    4> allocate auxiliary channel a3 type disk;
    5> allocate auxiliary channel a4 type disk;
    6> set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
    7> DUPLICATE DATABASE TO por02x
    8> BACKUP LOCATION '/backup_rman/backupset/por02p'
    9> NOFILENAMECHECK
    10> LOGFILE
    11> GROUP 1 ('+DB_REDO') SIZE 512M,
    12> GROUP 2 ('+DB_REDO') SIZE 512M,
    13> GROUP 3 ('+DB_REDO') SIZE 512M,
    14> GROUP 4 ('+DB_REDO') SIZE 512M,
    15> GROUP 5 ('+DB_REDO') SIZE 512M,
    16> GROUP 6 ('+DB_REDO') SIZE 512M,
    17> GROUP 7 ('+DB_REDO') SIZE 512M,
    18> GROUP 8 ('+DB_REDO') SIZE 512M;
    19> }
    allocated channel: a1
    channel a1: SID=49 device type=DISK
    allocated channel: a2
    channel a2: SID=98 device type=DISK
    allocated channel: a3
    channel a3: SID=146 device type=DISK
    allocated channel: a4
    channel a4: SID=194 device type=DISK
    executing command: SET until clause
    Starting Duplicate Db at 23-APR-2013 14:22:07
    contents of Memory Script:
    sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
    shutdown clone immediate;
    startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 2137886720 bytes
    Fixed Size 2221336 bytes
    Variable Size 503319272 bytes
    Database Buffers 1610612736 bytes
    Redo Buffers 21733376 bytes
    allocated channel: a1
    channel a1: SID=98 device type=DISK
    allocated channel: a2
    channel a2: SID=146 device type=DISK
    allocated channel: a3
    channel a3: SID=194 device type=DISK
    allocated channel: a4
    channel a4: SID=242 device type=DISK
    contents of Memory Script:
    sql clone "alter system set db_name =
    ''POR02P'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
    sql clone "alter system set db_unique_name =
    ''POR02X'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
    shutdown clone immediate;
    startup clone force nomount
    restore clone primary controlfile from '/backup_rman/backupset/por02p/POR02P_20130331_e7o5su4v_1_1.BAK';
    alter clone database mount;
    executing Memory Script
    sql statement: alter system set db_name = ''POR02P'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set db_unique_name = ''POR02X'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area 2137886720 bytes
    Fixed Size 2221336 bytes
    Variable Size 503319272 bytes
    Database Buffers 1610612736 bytes
    Redo Buffers 21733376 bytes
    allocated channel: a1
    channel a1: SID=98 device type=DISK
    allocated channel: a2
    channel a2: SID=146 device type=DISK
    allocated channel: a3
    channel a3: SID=194 device type=DISK
    allocated channel: a4
    channel a4: SID=242 device type=DISK
    Starting restore at 23-APR-2013 14:23:02
    channel a2: skipped, AUTOBACKUP already found
    channel a3: skipped, AUTOBACKUP already found
    channel a4: skipped, AUTOBACKUP already found
    channel a1: restoring control file
    channel a1: restore complete, elapsed time: 00:00:10
    output file name=+POR02U_CTL/por02x/control01.ctl
    Finished restore at 23-APR-2013 14:23:12
    database mounted
    channel a1: starting datafile backup set restore
    channel a1: specifying datafile(s) to restore from backup set
    channel a1: restoring datafile 00001 to +por02u_data
    channel a1: restoring datafile 00003 to +por02u_data
    channel a1: restoring datafile 00004 to +por02u_data
    channel a1: restoring datafile 00005 to +por02u_data
    channel a1: restoring datafile 00006 to +por02u_data
    channel a1: restoring datafile 00009 to +por02u_data
    channel a1: restoring datafile 00014 to +por02u_data
    channel a1: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
    channel a2: starting datafile backup set restore
    channel a2: specifying datafile(s) to restore from backup set
    channel a2: restoring datafile 00002 to +por02u_data
    channel a2: restoring datafile 00007 to +por02u_data
    channel a2: restoring datafile 00008 to +por02u_data
    channel a2: restoring datafile 00010 to +por02u_data
    channel a2: restoring datafile 00011 to +por02u_data
    channel a2: restoring datafile 00012 to +por02u_data
    channel a2: restoring datafile 00013 to +por02u_data
    channel a2: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
    channel a1: piece handle=/backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK tag=LEVEL0
    channel a1: restored backup piece 1
    channel a1: restore complete, elapsed time: 00:00:55
    channel a2: piece handle=/backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK tag=LEVEL0
    channel a2: restored backup piece 1
    channel a2: restore complete, elapsed time: 00:05:05
    Finished restore at 23-APR-2013 14:28:24
    channel a2: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
    channel a1: piece handle=/backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK tag=LEVEL1D
    channel a1: restored backup piece 1
    channel a1: restore complete, elapsed time: 00:00:35
    channel a2: piece handle=/backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK tag=LEVEL1D
    channel a2: restored backup piece 1
    channel a2: restore complete, elapsed time: 00:00:35
    starting media recovery
    unable to find archived log
    archived log thread=1 sequence=163
    released channel: a1
    released channel: a2
    released channel: a3
    released channel: a4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 04/23/2013 14:29:41
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 163 and starting SCN of 15660537
    RMAN> **end-of-file**
    So, if I go back to my source:
    RMAN> list backup of archivelog sequence 163 thread 1;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    11386318 66.51M DISK 00:00:09 31-MAR-2013 08:04:08
    BP Key: 11386330 Status: EXPIRED Compressed: YES Tag: ARCHIVE_BAK
    Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e9o5subf_1_1.BAK
    List of Archived Logs in backup set 11386318
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 163 15336390 31-MAR-2013 00:45:14 15661283 31-MAR-2013 08:03:51
    The archivelog is not reported as part of the preview
    command. Also, shouldn't it's changes be included in
    the next day's LEVEL1?
    Thanks for anyone's time. Would be happy to provide
    more info.

    Levi,
    Thank you very much for your insight.
    However, I may have found something. I have not fully tested and found a solution so I have not posted an update yet...I want to make sure I have a complete answer. However, I will provide some details.
    I decided to go ahead and restore ALL my archivelogs just to see if I could get the recovery to work.
    It still did not work!
    So, I happened to look at my alert log (can't believe I did not check it before) and I saw this:
    Wed Apr 24 13:34:20 2013
    Errors with log +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241
    Recovery interrupted!
    Recovered data files to a consistent state at change 17574527
    Media Recovery failed with error 19755
    Errors in file /opt/app/oracle/diag/rdbms/por02x/por02x/trace/por02x_pr00_2973744.trc:
    ORA-00283: recovery session canceled due to errors
    ORA-19755: could not open change tracking file
    ORA-19750: change tracking file: '+POR02P_DATA/por02p/changetracking/ctf.272.810127579'
    ORA-17503: ksfdopn:2 Failed to open file +POR02P_DATA/por02p/changetracking/ctf.272.810127579
    ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
    ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
    Slave exiting with ORA-283 exception
    Errors in file /opt/app/oracle/diag/rdbms/por02x/por02x/trace/por02x_pr00_2973744.trc:
    ORA-00283: recovery session canceled due to errors
    ORA-19755: could not open change tracking file
    ORA-19750: change tracking file: '+POR02P_DATA/por02p/changetracking/ctf.272.810127579'
    ORA-17503: ksfdopn:2 Failed to open file +POR02P_DATA/por02p/changetracking/ctf.272.810127579
    ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
    ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
    ORA-10877 signalled during: alter database recover logfile '+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241'...
    Then, I looked on Metalink and found this:
    Oracle Support Document 1098638.1 (Rman Duplicate fail ORA-19755, Tries Open The Block Change Tracking File of Source DB) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1098638.1
    [https://support.oracle.com/epmos/faces/DocumentDisplay?id=1098638.1]
    Now, this document is very interesting within the context of the problem I am having.  However, it says a few things:
    1. This is fixed in the oracle patchset 11.2.0.2 as part of Bug 7500916.
    ---I am on patchset 11.2.0.2!
    2. The workaround is to disable change tracking before duplicate.
    ---this is not really an option for me...we like having this turned on...it considerably speeds up our backups
    3. Workaround is to set DB_FILE_NAME_CONVERT in the SET-clause of duplicate, instead of using DB_FILE_NAME_CONVERT setting in an init.ora or spfile.
    ---tried this...did not work
    4. Workaround is to create a dummy file in the location where the error ORA-19755 is signalled.
    ---have not tried this yet
    Another interesting thing to note:
    My database is left in mounted state when it fails.  After seeing this document, just for fun I:
    SQL> alter database disable block change tracking;
    Database altered.
    And Then:
    RMAN> run {
    2> set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
    3> recover database;
    4> }
    executing command: SET until clause
    Starting recover at 24-APR-2013 14:20:20
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=98 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=146 device type=DISK
    starting media recovery
    archived log for thread 1 with sequence 181 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_181.7864.813591241
    archived log for thread 1 with sequence 182 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_182.2358.813591247
    archived log for thread 1 with sequence 183 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_183.3637.813591249
    archived log for thread 2 with sequence 149 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_149.9547.813591241
    archived log for thread 2 with sequence 150 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_150.9570.813591241
    archived log for thread 2 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_151.6148.813591247
    archived log for thread 3 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_151.9630.813591239
    archived log for thread 3 with sequence 152 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_152.4418.813591247
    archived log for thread 3 with sequence 153 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_153.9782.813591247
    archived log for thread 4 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241
    archived log for thread 4 with sequence 152 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_152.6936.813591241
    archived log for thread 4 with sequence 153 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_153.9610.813591249
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241 thread=4 sequence=151
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_181.7864.813591241 thread=1 sequence=181
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_149.9547.813591241 thread=2 sequence=149
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_151.9630.813591239 thread=3 sequence=151
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_150.9570.813591241 thread=2 sequence=150
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_152.6936.813591241 thread=4 sequence=152
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_182.2358.813591247 thread=1 sequence=182
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_152.4418.813591247 thread=3 sequence=152
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_183.3637.813591249 thread=1 sequence=183
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_153.9782.813591247 thread=3 sequence=153
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_151.6148.813591247 thread=2 sequence=151
    archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_153.9610.813591249 thread=4 sequence=153
    media recovery complete, elapsed time: 00:00:08
    Finished recover at 24-APR-2013 14:20:36
    So, it finishes the recovery. However, I did not yet try to open resetlogs because this was originally a duplicate and doing an open resetlogs would not complete all the post-duplicate operations.
    Also, looking at the logs applied when running the above recover, now it only uses logs that were specified in the original PREVIEW command.
    I am going to play around some more and I promise I will post back with whatever results I happen across.
    Chris..

  • Unable to find archived log

    Hi
    I am restoring a hot backup taken through RMAN using following commands:
    configure controlfile autobackup on;
    BACKUP DATABASE ;
    BACKUP ARCHIVELOG ALL DELETE INPUT;
    Now I am going to restore that using following commands:
    restore spfile from autobackup;
    restore controlfile from autobackup;
    shutdown immediate;
    startup mount;
    restore database;
    RECOVER DATABASE;
    ALTER DATABASE OPEN RESETLOGS;
    But it goes fine till restore database. At recover database I get following errors:
    archived log for thread 1 with sequence 2461 is already on disk as file /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_1_8fbs9bvt_.log
    archived log for thread 1 with sequence 2462 is already on disk as file /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_2_8fbs9chb_.log
    unable to find archived log
    archived log thread=1 sequence=545
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/11/2013 20:41:43
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 545 and starting SCN of 25891726
    I have checked the backup folder and there are only empty date wise folders under archivedlog folders.
    If I write RMAN> ALTER DATABASE OPEN RESETLOGS; I get:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 09/11/2013 20:43:01
    ORA-01190: control file or data file 1 is from before the last RESETLOGS
    ORA-01110: data file 1: '/u01/app/oracle/oradata/XE/system.dbf'
    If I write RMAN> recover database until sequence 545; I get
    Starting recover at 11-SEP-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=695 device type=DISK
    starting media recovery
    unable to find archived log
    archived log thread=1 sequence=545
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/11/2013 21:09:34
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 545 and starting SCN of 25891726
    I don't mind if some data is lost. Will be really thankful if someone can help me get my database open;
    Habib

    They way you are trying to recover will try to recover up to the last know SCN. Try to do a point in time recover up to a few minutes before the database was shutdown or crashed.
    Try something like this
    run{
    set until time "to_date('2013-09-11:00:00:00', 'yyyy-mm-dd:hh24:mi:ss')";
    restore spfile from autobackup;
    restore controlfile from autobackup;
    shutdown immediate;
    startup mount;
    restore database;
    RECOVER DATABASE;
    ALTER DATABASE OPEN RESETLOGS;

Maybe you are looking for