Doubt in - recover database command

Hello,
I wanted to know the significance of - using backup controlfile
in the sql command:
recover database using backup controlfile until cancel
Some background info-
I am performing a system copy using Db backup-restore methodology.
I generated a new control file using -
1. alter database backup controlfile to trace;
2. Editing the file, changing SID and renaming it to control.sql
3. @control.sql
So how is - recover database using backup controlfile until cancel
different from - recover database until cancel
in this scenario?
Thanks.

This is the best explanation i had found earlier which is well written
If you were to recover the database with a current control file, Oralce will know the last SCN of the last checkpoint. So Oracle can use the information in the archived and online redo logs to apply recovery up to that SCN. This is called a "complete" recovery.
If you do not have the current control file, your option is to use a backup controlfile. Which means Oracle does not know the SCN to stop applying recovery. So you tell Oracle that you are using a "backup controlfile" and that you will tell it when to stop applying redo by replying "cancel." When Oracle starts recovery, it looks at the datafiles to know the last time a checkpoint was performed on the datafile. Oracle now knows to start applying recovery to the datafile for all SCNs after the SCN in the datafile header. Oracle rolls forward transactions. But Oracle does not know when to stop, and eventually, Oracle applies recovery in all of your archived redo logs. You can then tell Oracle to use the redo in the online redo logs. Oracle will ask you where to find more redo. At this point, you tell it to quit applying redo by replying CANCEL.
Hope this helps in explaining the difference
Pravin

Similar Messages

  • Can I use RECOVER database command evenif there is no MEDIA FAILURE? [b]Urg

    I need an urgent help from all the big guns out there?
    My database is up and running, but still I want to recover the deletion of data that has been done on FRIDAY/SATURDAY/SUNDAY/MONDAY/TUESDAY/WEDNESDAY in other words I want the FRIDAY's state of the database.
    Can I do it using the
    "RECOVER DATABASE UNTIL TIME '2005-28-06-00:00:00' command?
    Please guide me.
    Thanks in advance

    Hi,
    i assume you running your database in archive log mode and using rman to accomplish you task.i would say that you can recover your database even if there is no media faliur occurs,no doubt you can use this.i think you want to recover your database to the fridays state prior to the table deletion,so you get the tables back in your database.so what's a problem execut following.
    run {
    SET UNTIL TIME "TO_DATE('apr 03 2005 01:17:13','MON DD YYYY HH24:MI:SS')";
    restore database ;
    recover database ;
    asuume in this example that you want to recover your database up to date aprail 3 and prior to 01pm time.
    change the code according to your requirement.
    thanks.

  • Doubt in Recover database until cancel

    Hi experts,
    One query, I want to try out recover database until cancel. But my archivelog files are in tape drive. How do i do it as it ask for archiver destination directory for the archivelog file.
    Or can any please explain how should i do it.
    Thanks in advance
    shaan

    Hi Satist,
    when i apply the other archivelog file, it again shows the error
    SQL> recover database until cancel using backup controlfile;
    ORA-00279: change 1740044 generated at 06/18/2007 21:20:18 needed for thread 1
    ORA-00289: suggestion : /oracle/NEWDB/admin/arch/1_5.dbf
    ORA-00280: change 1740044 for thread 1 is in sequence #5
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /oracle/NEWDB/admin/arch/1_30.dbf
    ORA-00310: archived log contains sequence 30; sequence 5 required
    ORA-00334: archived log: '/oracle/NEWDB/admin/arch/1_30.dbf'
    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/NEWDB/oradata/NEWDB/system.dbf'
    Please tell me why this happening or any solution for this. Moreover i have archivelog file
    from 1_1 to 1_14 .
    Thanks in advance
    shaan

  • Recovering database

    Hi,
    In our environment we sometimes copy "live" database from one disk volume to other. We use NetApp Snapmirror technology, but that is not important. That way, on the second volume we get a snapshot of that "live" database. What's obvious, the snapshot is inconsistent and before the copy database can be opened, needs recovery. We recover it using the "recover database" command. That solution we have been using for ages.
    The copied database usually performs recovery using redolog files. But yesterday, during recovery, the database asked us for archived redolog files (archived one day before). That was not a problem, we restored what was needed, but we couldn't deliver the "copy" database to users on time.
    I was asked to explain why the database needed the archived log files. My first explanation was "because the copy database was inconsistent as a result of long running transactions on the source database". But in my opinion undo data, to undo all uncommitted transactions is taken from undo tablespace. Nothing must have been redone. Can you explain me what the database had to redo? What could be the reason? Would you be so kind and give me advice how may I investigate the reason? In the future we have to deliver copied databases on time so there is a pressure put on me.
    Any help will be appreciated.
    Regards,
    Tim

    You don't mention a database version, but I presume you either do 'alter database begin backup' (if 10g) or 'alter tablespace ... begin backup' (if not 10g) before taking your mirror snapshot?
    If not, you're lucky to have had this thing working at all.
    If you issue those sorts of 'begin backup' commands, then there will be a database/tablespace checkpoint and the header blocks of the files involved will be updated with the latest checkpoint change number. During the recovery of your mirror, you will only need to roll those files forward from that point. The contents of the buffer cache for those files will be flushed to disk, and the copied files are therefore guaranteed to have contents no earlier than the header block's checkpoint change number.
    If you don't issue those sorts of commands, then Lord knows what state your datafile headers are in, and stuff in the buffer cache isn't necessarily flushed to disk in time. The copied file can therefore contain blocks from any checkpoint change number you care to think of onwards, and it's all pure chance what you get asked to supply by way of redo to rectify the situation.
    Recovery means rolling things forward as well as rolling them back: your comment about undo is a bit misguided therefore. You need undo and redo to be able to complete a recovery.

  • Recover Database in RMAN vs SQL*PLUS

    Hello,
    Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
    I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
    It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
    Thanks.
    h3. Solution Summary:
    The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
    Edited by: Dude on Jan 7, 2011 12:30 PM

    Dude wrote:
    I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
    Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
    C:\Documents and Settings\chinar>rman target sys/sm
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount;
    Oracle instance started
    Total System Global Area     138412032 bytes
    Fixed Size                     1247708 bytes
    Variable Size                 71304740 bytes
    Database Buffers              58720256 bytes
    Redo Buffers                   7139328 bytes
    RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
    ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
    2> ;
    Starting restore at 07-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=157 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
    Finished restore at 07-JAN-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 07-JAN-11
    Starting implicit crosscheck backup at 07-JAN-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 07-JAN-11
    Starting implicit crosscheck copy at 07-JAN-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 07-JAN-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
    1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
    restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
    restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
    restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
    \O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
    Finished restore at 07-JAN-11
    RMAN> recover database;
    Starting recover at 07-JAN-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    2.0\ORADATA\T\REDO02.LOG
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    media recovery complete, elapsed time: 00:00:03
    Finished recover at 07-JAN-11
    RMAN> exit
    Recovery Manager complete.
    C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    Database altered.
    SQL> And above you see lines as
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    *2.0\ORADATA\T\REDO02.LOG*
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
    alter database recover if needed
    start until cancel using backup controlfile
    Media Recovery Start
    parallel recovery started with 2 processes
    ORA-279 signalled during: alter database recover if needed
    start until cancel using backup controlfile
    Fri Jan 07 17:50:34 2011
    alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
    Fri Jan 07 17:50:34 2011
    Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
    Fri Jan 07 17:50:34 2011
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 665263
    Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start  until cancel using backup controlfile)
    And these is not any difference.
    Hope that help you and you got answer.

  • Error in Recover Database -  ORA-01547 , ORA-01194 and ORA-01110

    Hello folks,
    I am facing a problem when recovering a database..
    I made each tablespace in backup mode, then copied the datafile. I revert back the tablespace status to normal status.Once all datafiles are copied to target location, i created the control file from the source db.
    I started the target db by
    sqlplus "/ as sysdba"
    then i executed the control file
    SQL>@ctrlfile.sql
    Control file got created.
    SQL>recover database until cancel using backup controlfile;
    it asked for archives. I gave the path one by one until everything was done.Now i gave 'cancel' as below.
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    ORA-01112: media recovery not started
    Could anyone please tell me where I went wrong and how can I move ahead from this stage???
    Later on, when I gave open resetlogs, it gave the same error(as below)
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    Please let me know the mistake I made, how to avoid that and how to proceed now ???
    Thanks,
    Cherrish Vaidiyan
    [email protected]

    Hello Cherrish,
    A very good question you have asked. I hope you realize that you're doing an incomplete recovery. There is some amount of information that is still there in the online redo-log, that would not be applied on your target db. Moreover when you're using backup controlfile, you do not know till which point you need to apply archive logs.
    For incomplete recovery, Oracle for some reason has been very strict about the recover database command. i.e.
    recover database using backup controlfile
    recover database using backup controlfile until cancel
    Is not same. It also applies to the command that you had given. By giving the command 'recover database using backup controlfile until cancel', you're telling Oracle that incomplete recovery is in process, and you would do resetelogs, to make sure all files are in sync. This is required when you have lost the redo-logs
    In case you have just lost the control file. All latest redo-logs, archive-logs and datafiles are okay (or have been restored), then recover database using backup controlfile; would work perfectly okay. and resetlogs would not be required.. and that would be a complete recovery
    I hope this all makes sense to you
    Regards
    Sudhanshu

  • Recover database to new server problem

    Hi all,
    I'm running a production 10.2.0.4 DB in archivelog mode on Solaris 10.8. I used RMAN with a recovery catalog to execute the stored script:
    run{sql 'alter system archive log current';
    backup incremental level 0
    database archivelog all delete input;}
    I copied the rman files and spfile to a test server with the same directory structres. No Problem.
    Using "rman target /" I started the database in nomount and restored the controlfile from backup and mounted the database. No Problem.
    Still within the RMAN session, I restored the 1TB worth of datafiles. The restore completed, no problem.
    I then issued the command, "recover database;" PROBLEM, RMAN said datafile1 "System.dbf" needs more recovery to be in a consistent state.
    WHY? I issued the commands, "alter system archive log current;" and "archivelog all delete input" in my script.
    Why does it need the next archivelog to be consistent?
    I was under the impression that all I need to recover a database with rman was the output files from RMAN.
    I copied the next archivelog over and in SQLPLUS as SYS I issued the command, " recover database using backup controlfile until cancel;"
    I canceled the recovery when it asked for the next archivelog and opened database reset logs.
    If I didn't have access to the next archive log how would I solve this problem?

    Your BACKUP should be executed as BACKUP DATABASE PLUS ARCHIVELOG. The "PLUS ARCHIVELOG" causes Oracle to issue an ALTER SYSTEM SWITCH LOGFILE at the end of the database backup so that the ArchiveLog generated gets picked up by the subsequent Backup of the ArchiveLog as well.
    Your first RECOVER DATABASE command was attempting a Complete recovery. Had you specified an UNTIL clause, Oracle would know that you wanted an Incomplete recovery upto the last available archivelog. Your second RECOVER DATABASE with the UNTIL CANCEL was an Incomplete Recovery.
    Hemant K Chitale

  • RMAN Recover database error..

    Hi All,
    We were trying to restore and recover one of our databases. The restore went well but the recover is erroring out. Can someone please let us know what we should do to remedy this and carry on with the recovery.
    We got an error when we were trying to restore the controlfile at the begining (details below), but as you can see, it did manage to restore a copy of the controlfile successfully..
    Details below.
    C:\Users\oracle>rman target system/XXXX catalog rman/XXXX@rmancat
    Recovery Manager: Release 11.1.0.7.0 - Production on Thu Dec 2 08:31:03 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CODP (not mounted)
    connected to recovery catalog database
    RMAN> set dbid=2399577932
    executing command: SET DBID
    database name is CODP and DBID is 2399577932
    RMAN> RESTORE CONTROLFILE;
    Starting restore at 02-DEC-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=152 device type=DISK
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00
    channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
    "ORA-19505: failed to identify file D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    failover to previous backup
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1
    channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
    "ORA-19505: failed to identify file D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    failover to previous backup
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01 tag=TAG20101130T204059
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=C:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL01.CTL
    output file name=D:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL02.CTL
    output file name=D:\ORACLE\ORADATA\CODP\CONTROL03.CTL
    Finished restore at 02-DEC-10
    RMAN> RESTORE SPFILE FROM AUTOBACKUP;
    Starting restore at 02-DEC-10
    using channel ORA_DISK_1
    recovery area destination: D:\oracle\flash_recovery_area\
    database name (or database unique name) used for search: CODP
    channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101202
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101201
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101130
    channel ORA_DISK_1: AUTOBACKUP found: D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
    channel ORA_DISK_1: restoring spfile from AUTOBACKUP D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
    channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
    Finished restore at 02-DEC-10
    RMAN> restore database;
    Starting restore at 02-DEC-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00020 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T1.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00002 to D:\ORACLE\ORADATA\CODP\UNDOTBS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:03:25
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00009 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00010 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to D:\ORACLE\ORADATA\CODP\SYSTEM01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00005 to D:\ORACLE\ORADATA\CODP\PROD_T1_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00006 to D:\ORACLE\ORADATA\CODP\PROD_T2_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00007 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00025 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:36
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00024 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00026 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00027 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_04.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00011 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00030 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_07.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00028 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_05.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00029 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_06.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00003 to D:\ORACLE\ORADATA\CODP\SYSAUX01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00008 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00032 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00033 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00034 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00031 to D:\ORACLE\ORADATA\CODP\PROD_I1_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00004 to D:\ORACLE\ORADATA\CODP\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00021 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T2.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    Finished restore at 02-DEC-10
    RMAN> recover database;
    Starting recover at 02-DEC-10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 12/02/2010 09:08:05
    ORA-00210: cannot open the specified control file
    RMAN>Thanks

    Sorry everyone.. My bad.. I forgot to MOUNT the instance before trying to use the RECOVER DATABASE command.
    Thanks

  • Problem in recovering database

    I Have Oracle Database 10g (10.2.0.1.0) on Windows Server 2003
    I have taken full hot RMAN backup of database.
    I have copied the backup files from flash recovery area.
    I have one other Machine having windows server 2003 And Oracle 10g Same version. I have copied the backup files from first machine to Flash Recovery Area folder on second machine.
    Now i am trying to restore the database of first machine to second machine.
    1. I have created a new instance on second machice with same name as in fiirst machine.
    2. I have created one ORA password file as well.
    3. SET ORACLE_SID=<name of DB as it was in first machine>
    4. RMAN TARGET sys/<password given in newly ORA pwd file>@<DB name> nocatalog
    5. SET DBID=<dbid of old database>
    6. STARTUP NOMOUNT FORCE
    7. RESTORE SPFILE TO PFILE '<path of new pfile>' from '<path where backup files are there>';
    8. CREATE UDUMP,BDUMP,CDUMP,PFILE,ORADATA FOLDERS where required;
    9. SHUTDOWN IMMEDIATE;
    10. STARTUP NOMOUNT PFILE='<path of newly created pfile>';
    11 RESTORE CONTROLFILE FROM '<path of backup files>';
    12. ALTER DATABASE MOUNT;
    Everything work fine till here
    Now my next step was
    13. RESTORE DATABASE;
    Then it gives error like:-
    RMAN> restore database;
    Starting restore at 20-NOV-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=375 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/20/2008 21:00:54
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Firstly i copied backup files to flash recovery area, then i copied files to 'D:\oracle\product\10.2.0\db_1\database' as well. Because i have done it in 9i, in 9i i copied the backup files to this backup folder then while doing restore RMAN succesfully takes file from this folder & restores the database. but in 10g RMAN is not recognising the path of backup. How this problem can be solved? Or is this some different problem which i am not getting?
    Waiting for reply..

    Hi ORADBA,
    Thanks for your response. Your solution worked. Actually there was a difference the Oracle installation on server from which i was taking backup is on E drive.
    And the server on which i am trying to restore that database has Oracle installation files on D drive. That's why this confusion occurred.
    But i have one query again. I am not able to recover my database fully.
    Firstly i typed restore database command that worked. Thereafter i tried recover database command. that commant resulted in an error as given below. Than i typed command archive log list on SQL promt, from there i found the information of latest archive log. then i tried recover database until logseq 484 thread 1. That also didn't work. In the same situation i tried to open database i was able to open database using command alter database open resetlogs. I suppose i was not able to recover the database fully. Hi can i recover my database fully?
    waiting for reply. Thanks in advance.
    RMAN> recover database;
    Starting recover at 24-NOV-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting incremental datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF
    destination for restore of datafile 00002: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF
    destination for restore of datafile 00003: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF
    destination for restore of datafile 00004: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1
    MFNNND1_BACKUP_TESTDB_L_1_4LB0PZXS_.BKP*
    channel ORA_DISK_1: restored backup piece 1
    piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1_MF_NNND1_BACKUP_TESTDB_L_1_4L
    B0PZXS_.BKP tag=BACKUP_TESTDB_L_112008115509
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=484
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2008 19:47:07
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 484 lowscn 11013224
    RMAN> recover database until logseq 484;
    Starting recover at 24-NOV-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2008 19:48:07
    RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
    RMAN> recover database until logseq 484 thread 1;
    Starting recover at 24-NOV-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2008 19:48:20
    RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
    RMAN> recover database until logseq 483 thread 1;
    Starting recover at 24-NOV-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2008 19:48:58
    RMAN-06556: datafile 1 must be restored from backup older than scn 10973094
    RMAN> recover database until logseq 482 thread 1;
    Starting recover at 24-NOV-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2008 19:49:06
    RMAN-06556: datafile 1 must be restored from backup older than scn 10952975
    RMAN> alter database open;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 11/24/2008 19:49:21
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    RMAN> alter database open resetlogs
    *2> ;*
    Edited by: user648257 on Nov 24, 2008 6:48 AM

  • More than one "RECOVER DATABASE" session possible ?

    Can two separate rman sessions try to execute the "recover database" command at the same time or will the database forbid it ? (hopefully).
    Sorry but I am not in a position to test this currently.
    johnnied

    Many thanks Sybrand for your help on this.
    I managed to try it and the message is :-
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/16/2009 10:48:01
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
    start until cancel using backup controlfile
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery
    ORA-01110: data file 1: '+DATA/oracle/datafile/system.298.682412027'
    regs
    johnnied

  • Recover database with arc-file

    Hi,
    my database was in the archive-log and then we had a dataimport and the database crashed, because there was not enough space.
    So i brought the database now to the mount status and i want to recover my database.
    I take this:
    recover database using BACKUP CONTROLFILE
    and then it proposed me an archive-file but i must take an other one.
    How can i choose the file?
    Thanks in advance.
    Nicole

    And why on Earth are you throwing "using backup controlfile" in there?
    ARE you using a backed up copy of your controlfile? No. You haven't mentioned restoring an old copy of the controlfile at all. So if you haven't restored one from backup, why in Heaven's name are you telling Oracle that the control file is out of date? Because that's what that recovery command does.
    Once you say, "The control file you are using is not to be trusted regarding which logs have been generated because it's an old one I brought back from a backup made some time in the past", then it's no wonder that Oracle has a brain fit and starts proposing that archives be applied which don't actually exist yet. "Using backup controlfile" means "I will tell you when to stop applying redo, because this ancient controlfile can't do that for me reliably".
    It does actually get worse: the fact that your database crashes doesn't inevitably mean you have to recover a thing. Instance crashes are recovered from completely automatically just by restarting the database.
    So you probably didn't need to recover your database at all. You've used the wrong command to recover it even if it did. And by claiming your control file is out of date once, it is quite possible that you really do now need to perform a recovery that was originally completely unnecessary.
    Not bad for a day's work! :-)
    The golden rule of recoveries is: when you're in a hole, stop digging until you've worked out with near-complete certainty why you're in the hole in the first place. Diagnosis is king. Only then do you start planning recoveries.
    The second golden rule of any recovery process, once you've started is: only restore from backup those files which are actually damaged. If your control file isn't lost or damaged, it doesn't need restoring. Same goes for any datafile, too.
    And the third golden rule is: only recover that which you've restored. If you've restored file 4, you don't issue a "recover database" command. And if you haven't restored file 6, don't say 'recover datafile 6'. And if you haven't restored a binary copy of the controlfile made at some time in the past, don't say "using backup controlfile".
    The final, not so much rule as inevitable consequence, is that botched, mistaken, wrong or partial recoveries screw your database up much worse than it was before you did anything. I hope you have a good backup of this database, because you're going to need it.

  • Recover database using cold backup

    Hi All,
    One of the table is delete by one of our DBA from PROD accidentally. We have a cold backup on one day before.
    Now we are trying to restore it from the cold backup. PROD DB is in archivelog and all the archive is in tact.
    The table got truncated today at 8 PM. Can we apply the database till 8 PM so that we can restore the truncated table using cold backup.
    Please find the below steps which we are using to restore.
    creating controlfile
    starting the db in mount state
    recover database;
    Will it ask for latest archive log when we try to recover it.
    ENV details -
    DB - 11.2.0.1
    Please suggest.
    Thanks

    Hi,
    If you have doubts about the procedure to use to restore a backup to a point in time, then please take a look at the documentation first: Performing Flashback and Database Point-in-Time Recovery - 11g Release 2 (11.2)
    After you specify the time when the recovery must end (UNTIL clause in rman), then the RECOVER command will try to use the archivelogs needed.
    Before starting with this PITR operation, you should check if your database has flashback active, because it will be much easier to recover using it.
    This is also explained on the same document linked above.
    Regards.
    Nelson

  • Unable to recover database after rman recovery and database open resetlogs

    I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
    Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
    RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
    RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
    OPA-00600: ORA-00600: internal error code, arguments: ...
    The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
    ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
    ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
    I hope I have not dug myself into too deep of a hole here.
    Here is the trace from my most recent attempt.
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> list incarnation of database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 08/02/2011 15:49:04
    ORA-01507: database not mounted
    RMAN> restore controlfile from autobackup;
    Starting restore at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    recovery area destination: /opt/oracle/flash_recovery_area
    database name (or database unique name) used for search: LCRSDEV
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 02-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
    4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
    5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
    6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
    7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
    8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
    RMAN> restore database until scn 95676700;
    Starting restore at 02-AUG-11
    Starting implicit crosscheck backup at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 6 objects
    Finished implicit crosscheck backup at 02-AUG-11
    Starting implicit crosscheck copy at 02-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 02-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/02/2011 15:52:04
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> restore database;
    Starting restore at 02-AUG-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
    restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
    restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
    restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
    restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
    channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
    channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
    Finished restore at 02-AUG-11
    RMAN> recover database until scn 95676700;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:16:28
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> recover database;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
    unable to find archive log
    archive log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:25:04
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

    Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    *1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
    *2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
    *3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
    *4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
    *5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
    *6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
    *7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
    *8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
    *9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
    However if I restore the controlfile to the earlier version I am getting the following output from the process:
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
    Starting restore at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 03-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
    RMAN> restore database until scn 92348137;
    Starting restore at 03-AUG-11
    Starting implicit crosscheck backup at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 03-AUG-11
    Starting implicit crosscheck copy at 03-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 03-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/03/2011 12:53:19
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    Edited by: K Doyle on Aug 3, 2011 10:22 AM

  • What order are Archive logs restored in when RMAN recover database issued

    Ok, you have a run block that has restored your level-0 RMAN backup.
    Your base datafiles are down on disc.
    You are about to start recovery to point in time, lets say until this morning at 07:00am.
    run {   set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
    allocate channel d1 type disk;
    allocate channel d2 type disk;
    allocate channel d3 type disk;
    allocate channel d4 type disk;
    recover database;
    So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
    required and starts to restore the archive logs. All as expected and works.
    My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
    i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
    When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
    Any inputs on experience welcome. I am now drilling into the documentation for any references there.
    Thanks

    Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
    This is from interpreting the list backup of archivelog commands.
    Backupset = 122672
    ==============
    Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
    Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
    Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
    Backupset = 122677
    ==============
    Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
    Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
    Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
    So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
    Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
    Thanks for inputs. Answers some questions.

  • Recover database in NOarchivelog mode :)

    Hi all. How to recover a database wich is in noarchivelog mode? B-)
    Suppose,
    I have 3 redolog groups (with two members in each, the second members are located on another drive ). When first redo log group was 1/2 full I took a full backup. Then there were 2 switches from first to second and from second to third. Now the currnet redolog group - 3 (just started). At this point we faced media failer. How to roll forward changes using backup + online redologs?
    Edited by: Junior Oracle DBA on Oct 16, 2008 1:53 PM

    Restore your database cold backup (excluding redo logs).
    Then issue this command :
    RECOVER DATABASE USING BACKUP CONTROLFILE
    provide the names of the last ACTIVE / CURRENT Redo Logs in the database when Oracle prompts for an ArchiveLog.
    When Oracle has finished recovery to a consistent point in time, it will return to the command prompt without any error.
    Now issue this command :
    ALTER DATABASE OPEN RESETLOGS
    You would have a Complete Recovery.
    This is provided that Oracle had NOT cycled through all the Online Redo Logs since the time when the Cold Backup was taken. (If Oracle had cycled through all the Online Redo Logs, it would have overwrriten the oldest log because it wasn't in ArchiveLog mode).
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

Maybe you are looking for

  • Burning old .mov files in iMovie HD6 (iDVD)

    I have a number of old "movies" in the .mov format originally produced in iMovie02 and iMovie03 that I would like to burn again using the DVD burner in iLife06. Unfortunately the old .mov file when I do burn it produces a result with large pixels, et

  • PpixHandleUtilities.cpp_114

    Hello everyone, I usually edit in Windows Movie Maker - I find it easy to use, full of features and easy to manipulate to create mini-films. I'm no Peter Jackson but I am really getting into film making. I am a teacher and I offered to edit (for my s

  • Can not send e-mail on Mail 2.1

    I can receive all mail but when I try to send I get the message: This message could not be delivered and will reamin in your Outbox until it can be delivered. The sender address [email protected] was rejected by the server. I have just migrated to th

  • How do I tell if the license and serial have been activated on CS4?

    How do I tell if the license and serial number have been activated on CS4?

  • Apps cannot be installed because of missing signature (non-jailbroken iPhon

    I was working on my iPhone 4 with iOS 4.2 (the last one) for a while, when I called my phone operator to unlock the simlock. I followed the procedure, and I saved of my iPhone with iTunes, then restored it, then restored the backup with iTunes (last