Set until time clause to restore controlfile

Hello
How can I use "set until" clause to restore the controlfile ?
The database is already in archivelog mode.
RMAN>
run {
set until time "TO_DATE('2011-02-24 09:30:00','yyyy-mm-dd hh24:mi:ss')";
restore controlfile from autobackup;
RMAN>
RMAN> 2> 3> 4>
executing command: set until time
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 02/24/2011 09:52:54
ORA-01507: database not mountedThis is the rman backup log:
Starting Control File and SPFILE Autobackup at 24-FEB-11
piece handle=/oracle/ora1020/dbs/c-1270860316-20110224-01 comment=NONE
Finished Control File and SPFILE Autobackup at 24-FEB-11I can also confirm that it was backed up.
ls -l /oracle/ora1020/dbs/c-1270860316-20110224-01
-rw-r-----  1 oracle dba 7143424 Feb 24 09:25 /oracle/ora1020/dbs/c-1270860316-20110224-01

For Datafiles and ArchiveLogs :
SET UNTIL works because RMAN can query the Controlfile (that is already present) {OR the Catalog, if available} to determine the Database Incaranation and identify all the BackupSets, BackupPieces and SCNs for datafiles.
For Controlfiles :
SET UNTIL needs to be able to query a source or determine a default location. If a Catalog is available, it can query the catalog. In the absence of the catalog, it can only determine the expected location to restore from on the basis of the AUTOBACKUP location and FORMAT.
When you have AutoBackup to Disk, using an FRA and have the AUTOBACKUP FORMAT set correctly you will notice that the controlfile backups go to a directory that has the date as part of the directory name. RMAN can "query" the backups it finds in each of the folders in the autobackup location and determine the correct piece to restore from. This is predicated on the FORMAT being the expected format. That is why the example also shows how you set the FORMAT before you do the restore -- to "tell" RMAN what format to expect. (Remember that it has no repository -- controlfile or catalog -- to query so it doesn't know the backup piece names, unless they follow the expected location and format !)
All of this works well on disk. On tape, it has to actually send it's requests to the Medial Management Layer -- it is the Media Management Layer that maintains the catalog of tapes and files on tapes. (Remember that RMAN still doesn't have a repository that it can query !).
Going back to my earlier comment that SET UNTIL is used for Datafiles and Archivelogs : Because it is much easier for RMAN to query a known repository for all the information it needs.
Hemant K Chitale

Similar Messages

  • Using set until time for duplicate is extremely slow

    Whenever I do a duplicate using the set until time it takes forever to get started. The executing command: SET until clause takes about 20 minutes, and then when allocating channels it takes about 10 minutes per channel. Both db's are 10.2.0.3, and in archivelog mode. When I do just a plain duplicate database it runs through just fine, no pauses or anything. Can someone please poing me in the right direction or shed some light on this issue for me?
    Thanks!

    Hi,
    Here is what happens when I kick off the duplicate command with the run block:
    RMAN> run {
    2> set until time "to_date('Mar 14 2009 06:00:00','Mon DD YYYY HH24:MI:SS')";
    3> duplicate target database to DEST;
    4> }
    executing command: SET until clause
    using target database control file instead of recovery catalog
    Starting Duplicate Db at 17-MAR-09
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=3985 devtype=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: sid=3984 devtype=DISK
    allocated channel: ORA_AUX_DISK_3
    channel ORA_AUX_DISK_3: sid=3983 devtype=DISK
    allocated channel: ORA_AUX_DISK_4
    channel ORA_AUX_DISK_4: sid=3982 devtype=DISK
    allocated channel: ORA_AUX_DISK_5
    channel ORA_AUX_DISK_5: sid=3981 devtype=DISK
    It takes anywhere from 15 to 20 minutes to allocate each channel, then it proceeds with the restoring of datafiles from the last backup. After that is done then it switches all the files, then it does this to start the recovery of the archive logs:
    contents of Memory Script:
    set until time "to_date('Mar 14 2009 06:00:00','Mon DD YYYY HH24:MI:SS')";
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 17-MAR-09
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=3981 devtype=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: sid=3982 devtype=DISK
    allocated channel: ORA_AUX_DISK_3
    channel ORA_AUX_DISK_3: sid=3983 devtype=DISK
    allocated channel: ORA_AUX_DISK_4
    channel ORA_AUX_DISK_4: sid=3984 devtype=DISK
    allocated channel: ORA_AUX_DISK_5
    channel ORA_AUX_DISK_5: sid=3977 devtype=DISK
    again it takes about 15 to 20 minutes to allocate each channel.

  • Set until time WITH RMAN

    Hi
    I have tested the codes too but it doesn't seem to be able to recover the database (including the tablespace which I have dropped). Why?
    # RMAN backup
    run
    allocate channel ch1 type disk;
    sql 'alter system archive log current';
    backup format '/backup/orcl/%d_t%t_s%s_p%p'
    filesperset=4
    database;
    release channel ch1;
    RMAN > list backup;
    File LV Type Ckp SCN Ckp Time Name
    1 Full 4072944 06-JUL-05 /oracle/oradata/system01.dbf
    8 Full 4072944 06-JUL-05 /oracle/oradata/tools01.dbf
    12 Full 4072944 06-JUL-05 /oracle/oradata/test01.dbf
    # Drop tablespace
    drop tablespace test including contents;
    # RMAN Recovery
    shutdown immediate;
    startup mount;
    # time is set to after rman backup and before tablespace dropped
    RMAN>
    run {
    set until time "to_date('06-07-2005 16:50:00','dd-mm-yyyy hh24:mi:ss')";
    restore database;
    recover database;
    RMAN > list backup;
    File LV Type Ckp SCN Ckp Time Name
    1 Full 4072944 06-JUL-05 /oracle/oradata/system01.dbf
    8 Full 4072944 06-JUL-05 /oracle/oradata/tools01.dbf
    12 Full 4072944 06-JUL-05
    Why is the RMAN list empty for the deleted tablespace? That's the reason why there is nothing to reover from?

    check at sql prompt
    select substr(name,1,50),status
      2    from v$datafileYours test01.dbf file should have status recover and filename should be missing.
    Khurram

  • Determine set until time from particular backup set

    Hi Gurus,
    First of all thank you for everybody reading my question.
    I am using database control file instead of recovery catalog.
    database 10gr2
    10.2.0.3
    os is suse linux
    Is there way (any magic query)
    you can determine sec part correctly for set until time looking backup set:
    7544 B F A DISK 28-AUG-11 1 1 YES PROD_FULL_BKUP_08.28.2011
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK;
    #SET UNTIL SEQUENCE 10008 thread 1;
    SET UNTIL TIME "TO_DATE('28-Aug-2011 03:40:32', 'dd-mon-YYYY hh24:mi:ss')";
    DUPLICATE TARGET DATABASE TO "11demo"
    I try hit and try for determining sec part.
    is there a proven way.
    '28-Aug-2011 03:40:31' worked
    '28-Aug-2011 03:40:38' didn't
    '28-Aug-2011 03:40:35' didn't.
    1)
    I look os time stamp set for backup.
    -rw-r----- 1 oracle oinstall 9281626112 2011-08-28 03:40 o1_mf_nnndf_PROD_FULL_BKUP_08_75mxdb7v_.bkp
    2) I add start time(03:00:00) +elapsed time.
    channel ORA_DISK_1: backup set complete, elapsed time: 00:40:35
    thanks

    I can get
    " list backup of archivelog all"
    BS Key Size Device Type Elapsed Time Completion Time
    7576 1.51G DISK 00:05:04 02-SEP-11
    BP Key: 7576 Status: AVAILABLE Compressed: YES Tag: ROD_ARC_09.02.2011
    Piece Name: /u02/flash_recovery_area/ROD/backupset/2011_09_02/o1_mf_ annnn_ADVPROD_ARC_09.02.20_7616s3fm_.bkp
    List of Archived Logs in backup set 7576
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 205824 3898563613 01-SEP-11 3898573074 01-SEP-11
    you can get "SET UNTIL SEQUENCE thread "
    correctly,
    But How does one find out the exact time the backup was completed?
    I simply used the timestamp from the Rman backup as an approximate indicator.
    Oracle Error:
    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: system01.dbf'
    released channel: aux1
    released channel: aux2
    released channel: aux3
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/01/2011 12:53:48
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 13891 lowscn 4013222506 found to restore
    Edited by: 880674 on Sep 2, 2011 7:07 AM

  • Set until time  vs. flashback off ???

    I have Windows XP and have installed 10g 10.2.0.1.0
    If I use set until time "to_date('2010-07-29 11:00:00','yyyy-mm-dd hh24:mi:ss')";
    for recovering database; please see below. Do I need to turn off flashback such as "*alter database flashback off"*
    Thanks in advance.
    run {
    shutdown immediate;
    startup mount;
    set until time "to_date('2010-07-29 11:00:00','yyyy-mm-dd hh24:mi:ss')";
    restore database;
    recover database;
    alter database open resetlogs;
    }

    782150 wrote:
    I have Windows XP and have installed 10g 10.2.0.1.0
    If I use set until time "to_date('2010-07-29 11:00:00','yyyy-mm-dd hh24:mi:ss')";
    for recovering database; please see below. Do I need to turn off flashback such as "*alter database flashback off"*No

  • Set until time TO_DATE

    Hi,
    what is wrong with my syntaxe :
    RMAN> run {
    2> set until time TO_DATE("07/07/07 09:38:00","DD/MM/YY HH:MI:SS");
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "identifier": expecting one of: "double-quoted-string, equal, single-quoted-string"
    RMAN-01008: the bad identifier was: TO_DATE
    RMAN-01007: at line 2 column 16 file: standard input
    Can you help me please ?

    Duplicate post:
    RMAN ERROR when duplicating

  • How to set-up  Time Machine after Restore

    After having restored an entire system back from Time Machine, it looks to me as Time Machines wants to completely backup all data already held on the hard-disk. With this effect, the harddisk is not big enough. I do not want to buy another disk. Is there any way how to persuade Time Machine that it should use the existing data on the disk?

    Hi Aulia,
    I don't believe that you will be able to have Time Machine understand that you only want it to continue with the same data : once it has detected that a file changed, it makes another copy, even if you know that it's the same file : it's based on messages telling it that a file has changed, not on files comparison.
    I think that the "inprogress" file will be replaced by another one if you let TM do it's job : it won't make a third copy of your data. If there is enough space on the disk, you can let TM continue, and try to manage with the following trick, with patience and much care.
    Make sure that the "Action" menu is visible in a Finder's window (it is if you did not customize the toolbar to remove it), and dive into Time Machine. Select a item in the window : the Action menu now has an item that should read "delete all backups of this element" (or something like that : I'm translating my French version). Take care that "all" here really means ALL versions in the backup : the only copy left would be on your main disk.
    The next backup may not make a fresh copy unless you help it a little : after all, there was no message telling TM that the original was changed, since it was not ! Just do anything in the folder containing the item that you deleted from the backup (like creating and immediately deleting a folder there) : this will tell TM that something has happened there, the next backup will check the folder, detect the missing element and make a fresh copy.
    Having only one copy of a really important folder may not suit you, even if it's only for the short delay until the next backup. You can make a copy of it, and run TM to backup the copy (a right click on the icon in the dock shows a "backup now" item). You now have a backed up version, you can delete the original, and all the backup copies of the original with the previous method. But if you rename the copy back to it's original name, it will be saved again... just iterate one more time !
    I hope that this can help you, but please do not hesitate to try and validate your method on small copies before you delete something in your backup !
    PS : I just tested my proposals with my 33Gb iMovie Events folder : a new copy of an event folder is created in the backup each time you rename an event, and I gained more than 40 Gb by deleting all previous redundant versions.
    At least, it works for me !

  • RMAN restore using set until scn

    Hi guys.
    Quick question about using set until scn
    when I do list backup output shows multiple scn's for one full (I allocated 4 tape channels for the backup so there are 4 scn's in the output)
    Which one do I specify in the set until scn command? Below there is ..163 ...164 ...165 ...166
    Here is the backup I want to use:
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    12526 Incr 0 19G SBT_TAPE 00:27:22 Dec 31 2009 10:25:30
    BP Key: 12526 Status: AVAILABLE Tag: TAG20091231T095808
    Piece Name: rcworaprd-vprd2-full<12920:707047088:1>.dbf
    List of Datafiles in backup set 12526
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/system01.dbf
    11 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/ppa_data01.dbf
    12 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/ppa_index01.dbf
    13 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/itd_index01.dbf
    16 0 Incr 1697159163 Dec 31 2009 09:58:08 /u02/oradata/vprd2/rcl_data01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    12527 Incr 0 21G SBT_TAPE 00:29:19 Dec 31 2009 10:27:27
    BP Key: 12527 Status: AVAILABLE Tag: TAG20091231T095808
    Piece Name: rcworaprd-vprd2-full<12921:707047088:1>.dbf
    List of Datafiles in backup set 12527
    File LV Type Ckp SCN Ckp Time Name
    4 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/tools01.dbf
    7 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/xdb01.dbf
    8 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/user_index02.dbf
    9 0 Incr 1697159164 Dec 31 2009 09:58:08 /u02/oradata/vprd2/una_data01.dbf
    14 0 Incr 1697159164 Dec 31 2009 09:58:08
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    12528 Incr 0 29G SBT_TAPE 00:33:48 Dec 31 2009 10:31:57
    BP Key: 12528 Status: AVAILABLE Tag: TAG20091231T095808
    Piece Name: rcworaprd-vprd2-full<12923:707047089:1>.dbf
    List of Datafiles in backup set 12528
    File LV Type Ckp SCN Ckp Time Name
    6 0 Incr 1697159166 Dec 31 2009 09:58:09 /u02/oradata/vprd2/user_index01.dbf
    17 0 Incr 1697159166 Dec 31 2009 09:58:09 /u02/oradata/vprd2/rcl_index01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    12529 Incr 0 23G SBT_TAPE 00:38:09 Dec 31 2009 10:36:17
    BP Key: 12529 Status: AVAILABLE Tag: TAG20091231T095808
    Piece Name: rcworaprd-vprd2-full<12922:707047088:1>.dbf
    List of Datafiles in backup set 12529
    File LV Type Ckp SCN Ckp Time Name
    2 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/drsys01.dbf
    3 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/eng_data01.dbf
    5 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/user_data01.dbf
    10 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/una_index01.dbf
    15 0 Incr 1697159165 Dec 31 2009 09:58:09 /u02/oradata/vprd2/eng_index01.dbf
    Or would it be better to use the set until time... using the oldest time from the backupset 12529 (Dec 31 2009 10:36:17)
    All input is appreciated.
    Thanks
    Jamie

    Note that an online backup is an inconsistent backup:
    >
    Any backup taken when the database has not been shut down normally is an inconsistent backup. When a database is restored from an inconsistent backup, Oracle must perform media recovery before the database can be opened, applying any pending changes from the redo logs.
    As long as your database is running in ARCHIVELOG mode, and you back up your archived redo log files as well as your datafiles, inconsistent backups can be the foundation for a sound backup and recovery strategy. Inconsistent backups are an important part of the backup strategy for most databases, because they offer superior availability. For example, backups taken while the database is still open are inconsistent backups
    >
    If you need to restore your database using the listed backups, you need to apply the archived redo logs until a SCN which is greater than any SCN in the datafile backup sets: otherwise Oracle won't open the database because some datafiles may have different SCN.

  • How to determine Until Time in restore

    Hi I have read
    Restoring and Recovering with Recovery Manager on line:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrecov.htm
    I am not sure how to determine an Until Time during a restore, or in duplicating a database.
    Can someone show a specific example?
    The best thing I have found so far is this:
    SQL> select max(next_change#)
    from v$archived_log
    where archived='YES'
    group by thread#;
    OR
    SQL> select max(next_change#) from v$log_history;
    as documented here:
    RMAN-8060 Doing Duplicate Database on Recovered Database
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189394.1
    But that still leads to:
    RMAN-06025: no backup of log thread 2 seq 2817 scn 3193354318 found to restore
    RMAN-06025: no backup of log thread 2 seq 2816 scn 3192569562 found to restore
    RMAN-06025: no backup of log thread 2 seq 2815 scn 3191725873 found to restore
    RMAN-06025: no backup of log thread 1 seq 2437 scn 3191725871 found to restore
    errors about half the time during duplication.
    Thanks!
    -John

    Hi All,
    We use the following query against the RMAN recovery catalog in our RMAN DUPLICATE scripting to identify the latest time that we can use.
    SELECT TO_CHAR(MAX(recover_time),'DD-MON-RR HH24:MI:SS')
    FROM
    (SELECT b.completion_time recover_time
    FROM dbinc a, rc_backup_piece b
    WHERE a.db_key = b.db_key
    AND a.db_name = '${SSID}'
    AND b.backup_type in ('D','I')
    AND b.status = 'A'
    AND b.device_type = 'SBT_TAPE'
    AND b.tag IS NOT NULL
    AND b.tag != 'CTRLBKUP'
    AND b.tag NOT LIKE 'TAG%'
    UNION
    SELECT next_time recover_time
    FROM rc_backup_redolog
    WHERE db_name = '${SSID}');
    Additionally, you may need to account for a rare problem with the absolute_fuzzy_change# is higher than the checkpoint change number. Oracle Development said this should be fixed at some point in the future when I last talked with them on the topic in 02/2004.
    We've coded around it (we're using Oracle EE 9.2.0.5+) by adding a couple of minutes between the incr backup and the archivelog)
    Hope this helps,
    Rich

  • RMAN duplicate target using set until telling me it can not find data files

    I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
    I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
    However, whenever I try to execute the rman clone, it tells me for each datafile:
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
    Here is the RMAN script:
    spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
    #connect to catalog <catalog info>
    # target is the source and auxiliary is destination
    #connect target <put in source info here>
    #connect auxiliary /
    run {
    allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
    allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
    allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
    allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
    allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
    ##Archivelog number get from sql archive log list command
    #set until sequence 831;
    set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
    duplicate target database to CSPRSUM1 nofilenamecheck
    logfile
    group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
    group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
    group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
    Exit
    Here is the output:
    Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
    Recovery Manager11.1.0.7.0
    RMAN> #connect catalog <redacted info>>
    2> # target is the source and auxiliary is destination
    3> #connect target <redacted info>
    4> #connect auxiliary /
    5>
    6> run {
    7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
    8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
    9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
    10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
    11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
    12> ##Archivelog number get from sql archive log list command
    13> #set until sequence 831;
    14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
    15> duplicate target database to CSPRSUM1 nofilenamecheck
    16> logfile
    17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
    18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
    19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
    20> }
    starting full resync of recovery catalog
    full resync complete
    allocated channel: d1
    channel d1: SID=534 device type=DISK
    allocated channel: d2
    channel d2: SID=533 device type=DISK
    allocated channel: d3
    channel d3: SID=532 device type=DISK
    allocated channel: d4
    channel d4: SID=531 device type=DISK
    allocated channel: a1
    channel a1: SID=530 device type=DISK
    executing command: SET until clause
    Starting Duplicate Db at 15-JUN-11
    RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
    contents of Memory Script:
    set until scn 260398799;
    set newname for datafile 1 to
    "+data";
    set newname for datafile 2 to
    "+data";
    set newname for datafile 3 to
    "+data";
    set newname for datafile 4 to
    "+data";
    set newname for datafile 5 to
    "+data";
    set newname for datafile 6 to
    "+data";
    set newname for datafile 7 to
    "+data";
    set newname for datafile 8 to
    "+data";
    set newname for datafile 9 to
    "+data";
    set newname for datafile 10 to
    "+data";
    set newname for datafile 11 to
    "+data";
    set newname for datafile 12 to
    "+data";
    set newname for datafile 13 to
    "+data";
    set newname for datafile 14 to
    "+data";
    set newname for datafile 15 to
    "+data";
    set newname for datafile 16 to
    "+data";
    set newname for datafile 17 to
    "+data";
    set newname for datafile 18 to
    "+data";
    set newname for datafile 19 to
    "+data";
    set newname for datafile 20 to
    "+data";
    set newname for datafile 21 to
    "+data";
    set newname for datafile 22 to
    "+data";
    set newname for datafile 23 to
    "+data";
    set newname for datafile 24 to
    "+data";
    set newname for datafile 25 to
    "+data";
    set newname for datafile 26 to
    "+data";
    set newname for datafile 27 to
    "+data";
    set newname for datafile 28 to
    "+data";
    set newname for datafile 29 to
    "+data";
    set newname for datafile 30 to
    "+data";
    set newname for datafile 31 to
    "+data";
    set newname for datafile 32 to
    "+data";
    set newname for datafile 33 to
    "+data";
    set newname for datafile 34 to
    "+data";
    set newname for datafile 35 to
    "+data";
    set newname for datafile 36 to
    "+data";
    set newname for datafile 37 to
    "+data";
    set newname for datafile 38 to
    "+data";
    set newname for datafile 39 to
    "+data";
    set newname for datafile 40 to
    "+data";
    set newname for datafile 41 to
    "+data";
    set newname for datafile 42 to
    "+data";
    set newname for datafile 43 to
    "+data";
    set newname for datafile 44 to
    "+data";
    set newname for datafile 45 to
    "+data";
    set newname for datafile 46 to
    "+data";
    set newname for datafile 47 to
    "+data";
    set newname for datafile 48 to
    "+data";
    set newname for datafile 49 to
    "+data";
    set newname for datafile 50 to
    "+data";
    set newname for datafile 51 to
    "+data";
    set newname for datafile 52 to
    "+data";
    set newname for datafile 53 to
    "+data";
    set newname for datafile 54 to
    "+data";
    set newname for datafile 55 to
    "+data";
    set newname for datafile 56 to
    "+data";
    set newname for datafile 57 to
    "+data";
    set newname for datafile 58 to
    "+data";
    set newname for datafile 59 to
    "+data";
    set newname for datafile 60 to
    "+data";
    set newname for datafile 61 to
    "+data";
    set newname for datafile 62 to
    "+data";
    set newname for datafile 63 to
    "+data";
    set newname for datafile 64 to
    "+data";
    set newname for datafile 65 to
    "+data";
    set newname for datafile 66 to
    "+data";
    set newname for datafile 67 to
    "+data";
    set newname for datafile 68 to
    "+data";
    set newname for datafile 69 to
    "+data";
    set newname for datafile 70 to
    "+data";
    set newname for datafile 71 to
    "+data";
    set newname for datafile 72 to
    "+data";
    set newname for datafile 73 to
    "+data";
    set newname for datafile 74 to
    "+data";
    set newname for datafile 75 to
    "+data";
    set newname for datafile 76 to
    "+data";
    set newname for datafile 77 to
    "+data";
    set newname for datafile 78 to
    "+data";
    set newname for datafile 79 to
    "+data";
    set newname for datafile 80 to
    "+data";
    set newname for datafile 81 to
    "+data";
    set newname for datafile 82 to
    "+data";
    set newname for datafile 83 to
    "+data";
    set newname for datafile 84 to
    "+data";
    set newname for datafile 85 to
    "+data";
    set newname for datafile 86 to
    "+data";
    set newname for datafile 87 to
    "+data";
    set newname for datafile 88 to
    "+data";
    set newname for datafile 89 to
    "+data";
    set newname for datafile 90 to
    "+data";
    set newname for datafile 91 to
    "+data";
    set newname for datafile 92 to
    "+data";
    set newname for datafile 93 to
    "+data";
    set newname for datafile 94 to
    "+data";
    set newname for datafile 95 to
    "+data";
    set newname for datafile 96 to
    "+data";
    set newname for datafile 97 to
    "+data";
    set newname for datafile 98 to
    "+data";
    set newname for datafile 99 to
    "+data";
    set newname for datafile 100 to
    "+data";
    set newname for datafile 101 to
    "+data";
    set newname for datafile 102 to
    "+data";
    set newname for datafile 103 to
    "+data";
    set newname for datafile 104 to
    "+data";
    set newname for datafile 105 to
    "+data";
    set newname for datafile 106 to
    "+data";
    set newname for datafile 107 to
    "+data";
    set newname for datafile 108 to
    "+data";
    set newname for datafile 109 to
    "+data";
    set newname for datafile 110 to
    "+data";
    set newname for datafile 111 to
    "+data";
    set newname for datafile 112 to
    "+data";
    set newname for datafile 113 to
    "+data";
    set newname for datafile 114 to
    "+data";
    set newname for datafile 115 to
    "+data";
    set newname for datafile 116 to
    "+data";
    set newname for datafile 117 to
    "+data";
    set newname for datafile 118 to
    "+data";
    set newname for datafile 119 to
    "+data";
    set newname for datafile 120 to
    "+data";
    set newname for datafile 121 to
    "+data";
    set newname for datafile 122 to
    "+data";
    restore
    clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 15-JUN-11
    released channel: d1
    released channel: d2
    released channel: d3
    released channel: d4
    released channel: a1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
    RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 122 found to restore
    RMAN-06023: no backup or copy of datafile 121 found to restore
    RMAN-06023: no backup or copy of datafile 120 found to restore
    RMAN-06023: no backup or copy of datafile 119 found to restore
    RMAN-06023: no backup or copy of datafile 118 found to restore
    RMAN-06023: no backup or copy of datafile 117 found to restore
    RMAN-06023: no backup or copy of datafile 116 found to restore
    RMAN-06023: no backup or copy of datafile 115 found to restore
    RMAN-06023: no backup or copy of datafile 114 found to restore
    RMAN-06023: no backup or copy of datafile 113 found to restore
    RMAN-06023: no backup or copy of datafile 112 found to restore
    RMAN-06023: no backup or copy of datafile 111 found to restore
    RMAN-06023: no backup or copy of datafile 110 found to restore
    RMAN-06023: no backup or copy of datafile 109 found to restore
    RMAN-06023: no backup or copy of datafile 108 found to restore
    RMAN-06023: no backup or copy of datafile 107 found to restore
    RMAN-06023: no backup or copy of datafile 106 found to restore
    RMAN-06023: no backup or copy of datafile 105 found to restore
    RMAN-06023: no backup or copy of datafile 104 found to restore
    RMAN-06023: no backup or copy of datafile 103 found to restore
    RMAN-06023: no backup or copy of datafile 102 found to restore
    RMAN-06023: no backup or copy of datafile 101 found to restore
    RMAN-06023: no backup or copy of datafile 100 found to restore
    RMAN-06023: no backup or copy of datafile 99 found to restore
    RMAN-06023: no backup or copy of datafile 98 found to restore
    RMAN-06023: no backup or copy of datafile 97 found to restore
    RMAN-06023: no backup or copy of datafile 96 found to restore
    RMAN-06023: no backup or copy of datafile 95 found to restore
    RMAN-06023: no backup or copy of datafile 94 found to restore
    RMAN-06023: no backup or copy of datafile 93 found to restore
    RMAN-06023: no backup or copy of datafile 92 found to restore
    RMAN-06023: no backup or copy of datafile 91 found to restore
    RMAN-06023: no backup or copy of datafile 90 found to restore
    RMAN-06023: no backup or copy of datafile 89 found to restore
    RMAN-06023: no backup or copy of datafile 88 found to restore
    RMAN-06023: no backup or copy of datafile 87 found to restore
    RMAN-06023: no backup or copy of datafile 86 found to restore
    RMAN-06023: no backup or copy of datafile 85 found to restore
    RMAN-06023: no backup or copy of datafile 84 found to restore
    RMAN-06023: no backup or copy of datafile 83 found to restore
    RMAN-06023: no backup or copy of datafile 82 found to restore
    RMAN-06023: no backup or copy of datafile 81 found to restore
    RMAN-06023: no backup or copy of datafile 80 found to restore
    RMAN-06023: no backup or copy of datafile 79 found to restore
    RMAN-06023: no backup or copy of datafile 78 found to restore
    RMAN-06023: no backup or copy of datafile 77 found to restore
    RMAN-06023: no backup or copy of datafile 76 found to restore
    RMAN-06023: no backup or copy of datafile 75 found to restore
    RMAN-06023: no backup or copy of datafile 74 found to restore
    RMAN-06023: no backup or copy of datafile 73 found to restore
    RMAN-06023: no backup or copy of datafile 72 found to restore
    RMAN-06023: no backup or copy of datafile 71 found to restore
    RMAN-06023: no backup or copy of datafile 70 found to restore
    RMAN-06023: no backup or copy of datafile 69 found to restore
    RMAN-06023: no backup or copy of datafile 68 found to restore
    RMAN-06023: no backup or copy of datafile 67 found to restore
    RMAN-06023: no backup or copy of datafile 66 found to restore
    RMAN-06023: no backup or copy of datafile 65 found to restore
    RMAN-06023: no backup or copy of datafile 64 found to restore
    RMAN-06023: no backup or copy of datafile 63 found to restore
    RMAN-06023: no backup or copy of datafile 62 found to restore
    RMAN-06023: no backup or copy of datafile 61 found to restore
    RMAN-06023: no backup or copy of datafile 60 found to restore
    RMAN-06023: no backup or copy of datafile 59 found to restore
    RMAN-06023: no backup or copy of datafile 58 found to restore
    RMAN-06023: no backup or copy of datafile 57 found to restore
    RMAN-06023: no backup or copy of datafile 56 found to restore
    RMAN-06023: no backup or copy of datafile 55 found to restore
    RMAN-06023: no backup or copy of datafile 54 found to restore
    RMAN-06023: no backup or copy of datafile 53 found to restore
    RMAN-06023: no backup or copy of datafile 52 found to restore
    RMAN-06023: no backup or copy of datafile 51 found to restore
    RMAN-06023: no backup or copy of datafile 50 found to restore
    RMAN-06023: no backup or copy of datafile 49 found to restore
    RMAN-06023: no backup or copy of datafile 48 found to restore
    RMAN-06023: no backup or copy of datafile 47 found to restore
    RMAN-06023: no backup or copy of datafile 46 found to restore
    RMAN-06023: no backup or copy of datafile 45 found to restore
    RMAN-06023: no backup or copy of datafile 44 found to restore
    RMAN-06023: no backup or copy of datafile 43 found to restore
    RMAN-06023: no backup or copy of datafile 42 found to restore
    RMAN-06023: no backup or copy of datafile 41 found to restore
    RMAN-06023: no backup or copy of datafile 40 found to restore
    RMAN-06023: no backup or copy of datafile 39 found to restore
    RMAN-06023: no backup or copy of datafile 38 found to restore
    RMAN-06023: no backup or copy of datafile 37 found to restore
    RMAN-06023: no backup or copy of datafile 36 found to restore
    RMAN-06023: no backup or copy of datafile 35 found to restore
    RMAN-06023: no backup or copy of datafile 34 found to restore
    RMAN-06023: no backup or copy of datafile 33 found to restore
    RMAN-06023: no backup or copy of datafile 32 found to restore
    RMAN-06023: no backup or copy of datafile 31 found to restore
    RMAN-06023: no backup or copy of datafile 30 found to restore
    RMAN-06023: no backup or copy of datafile 29 found to restore
    RMAN-06023: no backup or copy of datafile 28 found to restore
    RMAN-06023: no backup or copy of datafile 27 found to restore
    RMAN-06023: no backup or copy of datafile 26 found to restore
    RMAN-06023: no backup or copy of datafile 25 found to restore
    RMAN-06023: no backup or copy of datafile 24 found to restore
    RMAN-06023: no backup or copy of datafile 23 found to restore
    RMAN-06023: no backup or copy of datafile 22 found to restore
    RMAN-06023: no backup or copy of datafile 21 found to restore
    RMAN-06023: no backup or copy of datafile 20 found to restore
    RMAN-06023: no backup or copy of datafile 19 found to restore
    RMAN-06023: no backup or copy of datafile 18 found to restore
    RMAN-06023: no backup or copy of datafile 17 found to restore
    RMAN-06023: no backup or copy of datafile 16 found to restore
    RMAN-06023: no backup or copy of datafile 15 found to restore
    RMAN-06023: no backup or copy of datafile 14 found to restore
    RMAN-06023: no backup or copy of datafile 13 found to restore
    RMAN-06023: no backup or copy of datafile 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to 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
    RMAN> Exit
    Recovery Manager complete.
    Edited by: kerrygm on Jun 15, 2011 11:36 AM

    Maybe making progress.
    I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    965689 Full 19.86M DISK 00:00:01 16-JUN-11
    BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
    Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
    SPFILE Included: Modification time: 16-JUN-11
    SPFILE db_unique_name: CSPROD
    Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
    BS Key Size Device Type Elapsed Time Completion Time
    966218 403.84M DISK 00:00:00 20-MAY-11
    BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
    Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
    List of Archived Logs in backup set 966218
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 2112 237027300 20-MAY-11 237046947 20-MAY-11
    1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
    1 2114 237059284 20-MAY-11 237216514 20-MAY-11
    1 2115 237216514 20-MAY-11 237709545 20-MAY-11
    1 2116 237709545 20-MAY-11 237722825 20-MAY-11
    1 2117 237722825 20-MAY-11 237730431 20-MAY-11
    1 2118 237730431 20-MAY-11 237860199 20-MAY-11
    I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
    Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
    Recovery Manager11.1.0.7.0
    RMAN> #connect catalog 'rmancat/rmancat@rmancat';
    2> # target is the source and auxiliary is destination
    3> #connect target sys/<pwd>@csprod
    4> #connect auxiliary /
    5>
    6> run {
    7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
    8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
    9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
    10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
    11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
    12> ##Archivelog number get from sql archive log list command
    13> set until sequence 237046947;
    14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
    15> duplicate target database to CSPRSUM1 nofilenamecheck
    16> logfile
    17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
    18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
    19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
    20> }
    allocated channel: d1
    channel d1: SID=532 device type=DISK
    allocated channel: d2
    channel d2: SID=533 device type=DISK
    allocated channel: d3
    channel d3: SID=531 device type=DISK
    allocated channel: d4
    channel d4: SID=555 device type=DISK
    allocated channel: a1
    channel a1: SID=534 device type=DISK
    executing command: SET until clause
    Starting Duplicate Db at 17-JUN-11
    RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
    contents of Memory Script:
    set until scn 373021170;
    set newname for datafile 1 to
    "+data";
    set newname for datafile 2 to
    Starting restore at 17-JUN-11
    channel d1: starting datafile backup set restore
    channel d1: specifying datafile(s) to restore from backup set
    channel d1: restoring datafile 00003 to +DATA
    channel d2: restoring datafile 00122 to +DATA
    channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
    channel d3: starting datafile backup set restore
    channel d3: specifying datafile(s) to restore from backup set
    channel d3: restoring datafile 00002 to +DATA
    channel d3: restoring datafile 00020 to +DATA
    channel d4: restoring datafile 00120 to +DATA
    channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
    channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
    channel d1: restored backup piece 1
    channel d1: restore complete, elapsed time: 00:01:15
    channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
    channel d4: restored backup piece 1
    channel d4: restore complete, elapsed time: 00:03:15
    channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
    channel d2: restored backup piece 1
    channel d2: restore complete, elapsed time: 00:03:35
    channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
    channel d3: restored backup piece 1
    channel d3: restore complete, elapsed time: 00:04:55
    Finished restore at 17-JUN-11
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
    MAXLOGFILES 23
    MAXLOGMEMBERS 3
    MAXDATAFILES 1021
    MAXINSTANCES 8
    MAXLOGHISTORY 584
    LOGFILE
    GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
    GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
    GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
    DATAFILE
    '+DATA/csprsum1/datafile/system.1535.754067379'
    CHARACTER SET WE8MSWIN1252
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
    datafile 121 switched to datafile copy
    input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
    datafile 122 switched to datafile copy
    input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
    contents of Memory Script:
    set until scn 373021170;
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 17-JUN-11
    starting media recovery
    Oracle Error:
    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: '+DATA/csprsum1/datafile/system.1535.754067379'
    released channel: d1
    released channel: d2
    released channel: d3
    released channel: d4
    released channel: a1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
    RMAN> Exit
    Recovery Manager complete.
    What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
    (e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
    Also, as you can see it was not able to do a media recovery.
    Thanks in advance for your help.

  • RMAN error when restoring controlfile from tape

    Hi,
    We have a Production database with instance name PROD.
    We use Symantec Netbackup software to backup this database to tape library.
    We want to test some recovery scenarios on a test server. So we want to restore the production backups from Tape to this test server.
    We did the following:
    Cloned the ORACLE Home to the Test Server.
    Changed the db_name parameter to PROD and also set ORACLE_SID to PROD.
    then we connected to RMAN and ran the following command to restore the control files:
    RMAN> run {
    set dbid 4155532403
    set controlfile autobackup format for device type 'sbt_type' to '%F';
    set until time "to_date('16/12/2012:10:13:37','dd/mm/yyyy:hh24:mi:ss')";
    allocate channel t1 device type 'sbt_tape';
    SEND 'NB_ORA_SERV=riysvbkp-001,NB_ORA_CLIENT=lh-erp';
    restore controlfile to '/testerp/dbexec/tmp/cf1.ctl' from autobackup;
    executing command: SET DBID
    database name is "PROD" and DBID is 4155532403
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    executing command: SET until clause
    allocated channel: t1
    channel t1: SID=171 device type=SBT_TAPE
    channel t1: Veritas NetBackup for Oracle - Release 7.1 (2011082510)
    sent command to channel: t1
    Starting restore at 17-DEC-12
    channel t1: looking for AUTOBACKUP on day: 20121216
    channel t1: AUTOBACKUP found: c-4155532403-20121216-01
    channel t1: restoring control file from AUTOBACKUP c-4155532403-20121216-01
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/17/2012 08:34:41
    ORA-19870: error while restoring backup piece c-4155532403-20121216-01
    ORA-19507: failed to retrieve sequential file, handle="c-4155532403-20121216-01", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Failed to process backup file <c-4155532403-20121216-01>
    Here you can see that AUTOBACKUP is found but RMAN is unable to process the backup piece.
    I am not able to see any errors in the log files. Please advise.
    Thanks,
    Muneer.

    Thanks.
    The earlier error is gone and now I am getting the following error:
    channel t1: looking for AUTOBACKUP on day: 20121216
    channel t1: AUTOBACKUP found: c-4155532403-20121216-01
    channel t1: restoring control file from AUTOBACKUP c-4155532403-20121216-01
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/17/2012 14:34:25
    ORA-19870: error while restoring backup piece c-4155532403-20121216-01
    ORA-19507: failed to retrieve sequential file, handle="c-4155532403-20121216-01", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Backup file <c-4155532403-20121216-01> not found in NetBackup catalog

  • How to fix RMAN-20207: UNTIL TIME is before RESETLOGS time

    Early this morning, in my haste to get a point in time restore and recovery started, I forgot to restore the controlfile as the 1st step.
    I used the current database control file, and now I have "RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME is before RESETLOGS time". I have a recovery catalog database. This is Oracle 8.1.7.4.
    Here was my script syntax:
    export ORACLE_SID=myname
    export ORACLE_HOME=/x01/oracle/product/8.1.7
    export LOG=/x01/admin/recover/point_in_time_${ORACLE_SID}_${TimeStamp}.log
    echo "Starting Time: `date`" > $LOG
    /x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
    set echo on;
    connect target
    connect catalog myuser/mypass@mycatalog
    startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
    alter database mount;
    run {
    set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
    allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    restore database;
    recover database;
    release channel t1;
    release channel t2;
    Alter Database Open Resetlogs;
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
    exit
    echo "Finished Time: `date`" >> ${LOG}
    Can I do the following to try to restore the controlfile? First, I would shutdown my database.
    export ORACLE_SID=myname
    export ORACLE_HOME=/x01/oracle/product/8.1.7
    export LOG=/x01/admin/rman/recover/db_point_in_time_8i_${ORACLE_SID}_${TimeStamp}.log
    echo "Starting Time: `date`" > $LOG
    /x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
    set echo on;
    connect target
    connect catalog myuser/mypass@mycatalog
    startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
    alter database mount;
    run {
    set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
    allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    restore controlfile to '/x01/disk/control01.ctl';
    replicate controlfile from '/x01/disk/control01.ctl';
    recover database;
    release channel t1;
    release channel t2;
    Alter Database Open Resetlogs;
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
    exit
    echo "Finished Time: `date`" >> ${LOG}
    I have a new incarnation of the database too -
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
    1 2 MYNAME 1849293826 NO 1 06-AUG-03
    1 25874 MYNAME 1849293826 NO 750748990 26-SEP-03
    1 143681 MYNAME 1849293826 NO 6610874669464 12-AUG-05
    1 265345 MYNAME 1849293826 YES 6611455777113 14-DEC-06
    What is the fastest way to fix this situation without having to restore the entire database?
    Thanks,
    Message was edited by:
    user521040

    Here is the "revised" script - I have not run this again on the Production system, but I might get a chance - finding corruption on the disk. I will test out later on a development database:
    #!/usr/bin/ksh
    TimeStamp=`date +%Y%m%d_%H%M%S`
    export ORACLE_SID=myname
    export ORACLE_HOME=/x01/oracle/product/8.1.7
    export LOG=/x01/admin/rman/recover/8i_${ORACLE_SID}_${TimeStamp}.log
    echo "Starting Time: `date`" > $LOG
    /x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
    set echo on;
    connect target
    connect catalog myuser/mypass@mycat1
    startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
    run {
    set until time "to_date('2006-11-25:18:08:00','yyyy-mm-dd:hh24:mi:ss')";
    allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    allocate channel t3 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    allocate channel t4 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
    restore controlfile to '/x01/disk/control01.ctl';
    replicate controlfile from '/x01/disk/control01.ctl';
    alter database mount;
    restore database;
    recover database;
    Alter Database Open Resetlogs;
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
    97217536";
    sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
    97217536";
    release channel t1;
    release channel t2;
    release channel t3;
    release channel t4;
    exit
    echo "Finished Time: `date`" >> ${LOG}
    Message was edited by:
    user521040

  • Restore controlfile,database(PIT)  from  backups(non-defualt location)

    Hi,
    Below is the script i m using to do db point-in-time recovery. But the problem is the backups was taken in a non-defualt location and i want the restore and recovery to be happened from there. Mostly facing issue with controlfile recovery. Just don't know how to tell RMAN that my controlfile rman backup is in non-defualt location '/fulldbbackup/'
    backup Script
    run{
            allocate channel ch1 device type disk ;
            backup database TAG = 'DR_test_backup' format '/fulldbbackup/%D_RMAN_DATAFILE_BACKUP_%U.bak';
            sql 'alter system archive log current';
            backup archivelog all delete input TAG = 'DR_test_backup2' format '/fulldbbackup/%D_RMAN_ARCHIVELOG_%U.bak';
         backup current controlfile TAG='DR_test_backup' format '/fulldbbackup/%D_RMAN_CURRENT_CONTROL_BACKUP_%U.bak';
    ==============================================================
    rman target / nocatalog
    RMAN> sql "alter session set nls_date_format = ''dd.mm.yyyy hh24:mi:ss''";
    RMAN> CROSSCHECK BACKUPPIECE TAG = 'DR_TEST_BACKUP';
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_CURRENT_CONTROL_BACKUP_0mnbvhlq_1_1.bak recid=22 stamp=784320186
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_ARCHIVELOG_0lnbvhlm_1_1.bak recid=21 stamp=784320184
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_ARCHIVELOG_0knbvhl2_1_1.bak recid=20 stamp=784320164
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_ARCHIVELOG_0jnbvhkp_1_1.bak recid=19 stamp=784320154
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_DATAFILE_BACKUP_0inbvhkf_1_1.bak recid=18 stamp=784320144
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/fulldbbackup/26_RMAN_DATAFILE_BACKUP_0hnbvhgn_1_1.bak recid=17 stamp=784320024
    Crosschecked 6 objectsRecovery Script (.ksh)
    #!/bin/ksh
    export ORACLE_SID=prod2
    echo $ORACLE_SID
    export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
    echo $ORACLE_HOME
    export PATH
    echo $PATH
    RMAN=$ORACLE_HOME/bin/rman
    $RMAN target sys/sys@prod2 nocatalog << EOF
    set dbid 1428819349;
    run {
    startup nomount;
    sql "alter session set nls_date_format = ''dd.mm.yyyy hh24:mi:ss''";
    allocate channel ch00 device type disk;
    allocate channel ch01 device type disk;
    set controlfile autobackup format for device type disk to '/fulldbbackup/26_RMAN_CURRENT_CONTROL_BACKUP_0mnbvhlq_1_1.bak';
    restore controlfile from autobackup;
    alter database mount;
    catalog start with '/fulldbbackup';
    set until time "to_date('26.05.2012 18:43:15','dd.mm.yyyy hh24:mi:ss')";
    restore database;
    recover database;
    alter database open resetlogs;
    release channel ch00;
    release channel ch01;
    exit;
    EOF
    echo "Completed"Thanks in advance

    You can restore control file by specifying the path explicitly.
    -- In the auxillary server
    Make sure you have the CONTROL_FILES parameter in the pfile. The control files will be restored to this path
    *.control_files='+LMNPROD_DG01/lmnprod/lmnprod_control01.ctl','+LMNPROD_DG01/lmnprod/lmnprod_control02.ctl','+LMNPROD_DG01/lmnprod/lmnprod_control03.ctl'Create spfile from pfile. Then
    SQL> conn / as sysdba
    Connected to an idle instance.
    SQL> startup nomount
    SQL> show parameter spfileStep5. Restore Control file
    The below command will create all the 3 control files mentioned in CONTROL_FILES parameter in the spfile.
    $ rman target /
    restore controlfile from '/path_where_bkp_piece_is_stored/RMAN_CURRENT_CONTROL_BACKUP_0mnbvhlq_1_1.bak';After restoring the control file and mounting the DB , you can use CATALOG command to catalog backup pieces

  • RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

    Hello,
    i am working for a scenerio and you can see my restore script below,
    RMAN> RUN
    2> {
    3> SET UNTIL TIME "to_date('24-05-2010 18:00:00','DD-MM-YYYY HH24:MI:SS')";
    4> RESTORE DATABASE;
    5> RECOVER DATABASE;
    6> }
    executing command: SET until clause
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 05/26/2010 11:23:24
    RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
    also you can see my backups,
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    89 B 1 A DISK 24-05-2010 15:36:04 1 1 NO BACKU
    P_BISE1DB_000_052410030823
    90 B 1 A DISK 24-05-2010 15:36:13 1 1 NO BACKU
    P_BISE1DB_000_052410030823
    91 B 0 A DISK 25-05-2010 12:01:09 1 1 NO TAG20
    100525T113815
    92 B 0 A DISK 25-05-2010 12:01:13 1 1 NO TAG20
    100525T113815
    93 B 1 A DISK 25-05-2010 12:01:55 1 1 NO TAG20
    100525T120152
    94 B 1 A DISK 25-05-2010 12:04:55 1 1 NO TAG20
    100525T120451
    95 B 1 A DISK 25-05-2010 13:55:00 1 1 NO TAG20
    100525T134431
    96 B 1 A DISK 25-05-2010 13:55:09 1 1 NO TAG20
    100525T134431
    97 B 1 A DISK 25-05-2010 14:01:43 1 1 NO TAG20
    100525T140139
    98 B 1 A DISK 25-05-2010 14:55:33 1 1 NO TAG20
    100525T140356
    so i am trying to understand that what is the earliest date that i can restore my database and avoid tihs error, according to the my backup sets?
    thank you
    Ugur

    Please query the following query and specify the RESETLOGS time
    SELECT RESETLOGS_TIME FROM v$database;
    i cant have result with this, because database is mount state,
    And post the result of the following command to provide an information about database incarnations:
    RMAN>LIST INCARNATION
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 BISE1DB 4092555014 PARENT 1116016 01-05-2007 16:22:55
    2 2 BISE1DB 4092555014 PARENT 1226717 14-12-2007 15:28:11
    3 3 BISE1DB 4092555014 PARENT 5783997202 04-05-2010 09:59:11
    4 4 BISE1DB 4092555014 CURRENT 5785721070 26-05-2010 10:59:32
    thank you

  • Recovery until time, I don't understand where is my error....

    Hi All,
    sorry but I don't understand....
    I need to restore one full backup for recover until time at 18-nov of all database on a second server
    I'v a new server with the same oracle version and the same directory structure of the primary server. Oracle is 11.2.0.2.
    I've daily full backup, and in a zffsa storage I've all copy of last 3 day of backup; The second server access to the samce zfssa storage.
    With list backup I can see backup about 18 november and I can see backup about 19 november.
    How I can select backup about 18 november and restore only this?
    I've the same AMS structure, too.
    Can i restore all db and recover until time?
    Edited by: ggiulian on 19-nov-2012 16.03

    For example,
    in the second server, i start in nomount a duplicate instance, restore controlfile from backup, and startup mount.
    After, i connect to rman target / auxiliary /
    and run:
    run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    set until time "to_date('18-nov-2012 13:00:00','dd-mon-rrrr hh24:mi:ss')";
    restore database;
    recover database;
    I receive
    RMAN-03002: failure of restore command at 11/20/2012 01:44:21
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 16 found to restore
    RMAN-06023: no backup or copy of datafile 15 found to restore
    RMAN-06023: no backup or copy of datafile 14 found to restore
    RMAN-06023: no backup or copy of datafile 13 found to restore
    RMAN-06023: no backup or copy of datafile 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore

Maybe you are looking for

  • Trigger internal serial nos creation for inbound delivery using DELVRY03

    Hi all, I am working in ECC 6.0 I need to update serial nos in the inbound delivery. The internal serial nos. that will be generated by the system, I have to trap them for a given delivery and map it to a set of external serial nos.(length is 40 char

  • Program to activate trasformation in BI&

    Hi All, Could anyone please tell me if there is any standard ABAP program through which we can activate transformations in BI7. Currently i have to reactivate some transformation in Production systems so immediate response would be highly appreciated

  • How to view when a table was last used!!?

    Hi, Pls let me know where I can view when a table in the database was last utilitized i.e. any selection or manipulation was performed on it. Thanks in Advance, Abhi

  • Re: Very slow or non-existent broadband in the eve...

    I am having the same problem, every evening usually between 9 pm and 10 pm but at other time as well. Slower at other times in the evening as well.  I consider that the problem is serious enough that BT have not fullfilled their part of the contract.

  • Specify dynamic url in htmlText

    I am populating a dynamic text box with some information that comes from an xml. //fill in the text      infoBox.informationText.htmlText=      "<font size='16' color='#FFFAF0'>"+calledMarkerIndex+      "\n<font size='14' color='#FFFAF0'>"+calledMark