Failure of duplicate - ORA -06054

Hi,
After a backup, we have a duplicate script running to copy it over to other server.
Sometimes, when there is extra activity on the db and the backup takes longer, the duplicate fails with this:
RMAN-03002: failure of Duplicate Db command at 04/08/2009 03:06:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown log: thread 1 seq 35238 lowscn5968228973373
Can someone explain the meaning of this error? Is it as simple as delaying the timing of the duplicate for much later in the morning ?
Thanks,
DA

The short answer is probably yes, you ought to be able to confirm by querying the primary for when that log was generated.
You don't say what your script actually does, but when I've done this in the past the duplicate has been
run {
set until time '<Some well known time eg 6am>'
duplicate target to ....
}rather than
run {
duplicate target to ....
}what then you need to watch out for is when the backup fails and you spend most of the day applying yesterdays archives to the duplicate!
Niall Litchfield
http://www.orawin.info/
Dan A wrote:
Hi,
After a backup, we have a duplicate script running to copy it over to other server.
Sometimes, when there is extra activity on the db and the backup takes longer, the duplicate fails with this:
RMAN-03002: failure of Duplicate Db command at 04/08/2009 03:06:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown log: thread 1 seq 35238 lowscn5968228973373
Can someone explain the meaning of this error? Is it as simple as delaying the timing of the duplicate for much later in the morning ?
Thanks,
DA

Similar Messages

  • Failure of Duplicate Db command 11g R2

    I have a RAC production(prod) database (11G R2) and created Auxiliary(cscp) database on different server and both have same Solaris 10 platforms. I cannot clone the database using “UNTIL TIME”. I do followings but get error. I would appreciate your help. I am running command from Auxiliary. Should I run RMAN from Prod server?
    In Aux Server:
    1-     Moved password file
    2-     Created init.ora and has following value
    DB_NAME='cscp'
    3-     startup nomount pfile='/apps/oracle/ora112/dbs/init.ora';
    in prod Server:
    1-     connect target sys/pw@prod
    2-     connect auxiliary sys/pw@cscp;
    3-     connect catalog rman/pw@prod;
    4-     RUN {
    SET NEWNAME FOR DATABASE TO "/apps/oracle/ora112/oradata/%U";
    DUPLICATE TARGET DATABASE TO CSCP pfile=/apps/oracle/ora112/dbs/init.ora
    SPFILE
    NOFILENAMECHECK
    UNTIL TIME "to_date('08-09-2010 13:03:14','dd-mm-yyyy hh24:mi:ss')"
    LOGFILE
    GROUP 1 ('/apps/oracle/ora112/redo01a.log') SIZE 50M REUSE,
    GROUP 2 ('/apps/oracle/ora112/redo02a.log') SIZE 50M REUSE;
    Here is the output:
    executing command: SET NEWNAME
    Starting Duplicate Db at 30-SEP-10
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=5 device type=DISK
    contents of Memory Script:
    set until scn 3958980184;
    restore clone spfile to '/apps/oracle/ora112/dbs/spfilecscp.ora';
    sql clone "alter system set spfile= ''/apps/oracle/ora112/dbs/spfilecscp.ora''";
    executing Memory Script
    executing command: SET until clause
    Starting restore at 30-SEP-10
    using channel ORA_AUX_DISK_1
    WARNING: A restore time was estimated based on the supplied UNTIL SCN
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring SPFILE
    output file name=/apps/oracle/ora112/dbs/spfilecscp.ora
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/30/2010 09:16:24
    RMAN-03015: error occurred in stored script Memory Script
    ORA-03113: end-of-file on communication channel

    Hi Maxym,
    I used following command and to verify backup files then copy them to other server. I get error. Do you have any suggestions what I get Controllfile is not found?
    RMAN> restore database preview until time "to_date('01-10-2010 22:26:30','dd-mm-yyyy hh24:mi:ss')";
    When I run Duplicate database command, there was following error generated by the RMAN:
    executing command: SET NEWNAME
    Starting Duplicate Db at 04-OCT-10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/04/2010 13:54:55
    RMAN-05575: CONTROLFILE backup created before to_date('01-10-2010 22:26:30','dd-mm-yyyy hh24:mi:ss') not found in /mnt
    After that, I run following command and copied the control file to other server and run duplicate command but still I get same error from rman.
    RMAN> restore controlfile preview until time "to_date('01-10-2010 22:26:30','dd-mm-yyyy hh24:mi:ss')";
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    7350 Full 18.92M DISK 00:00:03 01-OCT-10
    BP Key: 7360 Status: AVAILABLE Compressed: NO Tag: TAG20101001T011209
    Piece Name: +DATA/cs01/autobackup/2010_10_01/s_731207529.613.731207531
    Control File Included: Ckp SCN: 3981788360 Ckp time: 01-OCT-10

  • RMAN-03002: failure of Duplicate Db command at 06/01/2013 16:47:33

    sql statement: alter system reset db_unique_name scope=spfile
    Oracle instance shut down
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/01/2013 16:47:33
    RMAN-05501: aborting duplication of target database
    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 8064 and starting SCN of 13048058320848 found to restore
    i am trying to duplicate a database, at the end it is getting finished with this error.
    can any one help me fixing this one?

    It is preferable to set an UNTIL point (to the latest available archivelog) when doing a DUPLICATE. Else, Oracle attempts a complete recovery and fails after the last archivelog it finds.
    Hemant K Chitale

  • Online backup failure due to ORA-27086: unable to lock file - already in us

    Hi All,
      Online backup has failed due to the error
    =========================================================
    BR0301E SQL error -27086 at location BrInitOraCreate-5, SQL statement:
    '/* BRBACKUP AT PROF_CONN */ CREATE PFILE = '/oracle/SID/102_64/dbs/sap.ora' FROM SPFILE = '/oracle/SID/102_64/dbs/spfileSID.o
    ra''
    ORA-27086: unable to lock file - already in use
    IBM AIX RISC System/6000 Error: 13: Permission denied
    Additional information: 8
    Additional information: 1388548
    BR0303E Determination of Oracle version failed
    ==========================================================
    Please suggest.

    Check the file permissions on your Oracle_home...
    And kill all the processes, which already running for backup..
    Regards,
    Nick Loy

  • ORA 600, duplicate from RAC to NON-RAC

    Hi Experts,
    I'm trying to restore Production database for development purpose point in time recovery
    environment:
    ASM: 11gR1
    DB: 10gR2
    At the end of internal duplicate steps i have faced error
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/16/2010 05:37:06
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01152: file 3 was not restored from a sufficiently old backup
    ORA-01110: data file 3: '+DG1/dev/datafile/sysaux.534.737875511'Later i try to apply archives from production.. i have copied those and i started recovery .. i faced internal errors.
    SQL> recover database using backup controlfile;
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [],
    [], [], [], [], []after a lot of workaround i found one doc from metalink
    *Duplicate from active database raises ORA-01194 if one thead is closed [ID 1059699.1]*
    but i checked thread status by gv$thread.. it is looking open from last month..
    any other way to find closed threads?
    so what could be the reason.
    I have no time to raise an SR now.. any ideas will be highly appriciated.
    Thanks
    Edited by: CKPT on Dec 17, 2010 11:09 PM

    I am about to use this hidden parameter (_allow_resetlogs_corruption=true
    ) due to the almost identical problem you experienced.
    What are the risks and what next to do when I open the database?There is lot of RISK
    I tried to recover manually using existing archives, But no use.
    Raised an SR. as a last option provided by support and used that parameter, But this parameter is not suggestible, Before doing such thing, better to take backup of database(mount - cold backup).
    This thread is almost 7 months old, if you have any issue create a new thread.

  • Duplicate database failure

    RMAN-00571: =============================
    RMAN-00569: ==ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =============================
    RMAN-03002: failure of Duplicate Db command at 03/05/2004 14:59:50
    RMAN-03015: error occurred in stored script Memory Script
    ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
    ORA-19511: Error received from media manager layer, error text:
    sbtclose2: Failed to process backup file.
    ORA-19504: failed to create file "/oradata/inkdb/data/ink_tab/ink_OP001.dbf"
    ORA-17502: ksfdcre:4 Failed to create file /oradata/inkdb/data/ink_tab/ink_OP001.dbf
    ORA-17500: ODM err:File too large
    Actually i'm trying to Duplicate the Database to a different Host. I checked all User Rights and permissions as well as the path. Also enough Space is available (170GB for a 2GB File).

    Apply this command and post the results:
    df /oradata/inkdb/data/ink_tab
    ls -la /oradata/inkdb/data/ink_tab
    Joel Pérez

  • ORA-00119,ORA-00132 during duplicate target database for standby in 11gR2

    I am running
    duplicate target database for standby from active database
    command from RMAN.
    I went thru step-by-step on how to create a standby database from the textbook i got from my Oracle Univ. 11g Data Guard course. I set up all the listener.ora and tnsnames.ora files using netmgr, but I'm getting local_listener error.
    Here's what I am running in rman:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'kyledb','kylerep'
    set db_unique_name='kylerep'
    set db_file_name_convert='/kyledb/','/kylerep/'
    set log_file_name_convert='/kyledb/','/kylerep/'
    set control_files='/oradata/kylerep/control01.ctl'
    set log_archive_max_processes='4'
    set fal_client='kylerep'
    set fal_server='kyledb'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(kyledb,kylerep)'
    set log_archive_dest_1='service=kyledb ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=kyledb'
    And here's the error i get:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/12/2010 17:33:28
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_KYLEDB'
    result of
    SQL>show parameter local_listener;
    is
    NAME TYPE VALUE
    local_listener string LISTENER_KYLEDB
    entry in my listener.ora is
    SID_LIST_KYLEDB_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = kyledb.kyledev.usms.doj.gov)
    (ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = kyledb)
    ADR_BASE_KYLEDB_LISTENER = /app/oracle
    KYLEDB_LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    and entry in tnsnames.ora file is
    KYLEREP =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledbdev.usms.doj.gov)(PORT = 7898))
    (CONNECT_DATA =
    (SERVICE_NAME = kylerep.kyledbdev.usms.doj.gov)
    KYLEDB =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = kyledb.kyledev.usms.doj.gov)
    LISTENER_KYLEDB =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    Can anyone help me figure out what went wrong?
    Thanks in advance....

    I had the same problem,
    I Define TNS_ADMIN environment on script an resolve my problem.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 10/08/2010 17:21:15
    RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_DESENV2'
    In my shell increase the Environment:
    ## VARIAVEIS
    export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db1
    export PATH=$ORACLE_HOME/bin:$PATH
    export TNS_ADMIN=/u01/app/oracle/product/10.2.0/asm1/network/admin
    export ORACLE_SID=$1
    ## CHAMADA RMAN
    rman target / log=/u02/backup/db$1/bkp_cold-$1.log cmdfile=/home/oracle/script/rman/cold_backup/cold_backup.rcv
    After this:
    RMAN> run{
    2> shutdown immediate;
    3> startup force mount;
    4> backup database include current controlfile tag 'BKP_COLD_FULL';
    5> alter database open;
    6> delete obsolete;
    7> }
    8>
    9>
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    Oracle instance started
    database mounted
    Total System Global Area 1073741824 bytes
    Fixed Size 2089400 bytes
    Variable Size 264244808 bytes
    Database Buffers 801112064 bytes
    Redo Buffers 6295552 bytes
    Hope this helps and sorry for my terrible English! =)

  • ORA:01013 with Duplicate Database - RMAN

    Hi,
    I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
    server1 in open status and server2 in nomount state.
    the command i ran was:
    duplicate target database to clonedb
    until logseq 338 thread 1
    pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
    logfile
    '/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
    '/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
    Please let me know how to overcome this error..
    Thanks,
    Raj
    This is the error i got along with the log it created...
    Starting Duplicate Db at 28-OCT-04
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=14 devtype=DISK
    printing stored script: Memory Script
    set until scn 130734;
    set newname for datafile 1 to
    "/u02/oradata/clonedb/system01.dbf";
    set newname for datafile 2 to
    "/u03/oradata/clonedb/undotbs01.dbf";
    set newname for datafile 3 to
    "/u02/oradata/clonedb/testtbs_01.dbf";
    set newname for datafile 4 to
    "/u02/oradata/clonedb/system02.dbf";
    set newname for datafile 5 to
    "/u02/oradata/clonedb/rmantbs_01.dbf";
    restore
    check readonly
    clone database
    executing script: 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
    Starting restore at 28-OCT-04
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
    restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
    restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
    channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
    MAXLOGFILES 5
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 1
    MAXLOGHISTORY 680
    LOGFILE
    GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
    GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
    DATAFILE
    '/u02/oradata/clonedb/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    printing stored script: Memory Script
    switch clone datafile all;
    executing script: Memory Script
    datafile 2 switched to datafile copy
    input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
    datafile 4 switched to datafile copy
    input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
    datafile 5 switched to datafile copy
    input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
    printing stored script: Memory Script
    set until scn 130734;
    recover
    clone database
    delete archivelog
    executing script: Memory Script
    executing command: SET until clause
    Starting recover at 28-OCT-04
    using channel ORA_AUX_DISK_1
    starting media recovery
    channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
    printing stored script: Memory Script
    shutdown clone;
    startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
    executing script: Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
    Recovery Manager complete.

    HI,
    # STBY:
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area  242208768 bytes
    Fixed Size            2227176 bytes
    Variable Size          184550424 bytes
    Database Buffers       50331648 bytes
    Redo Buffers            5099520 bytes
    # PRIMARY:
    RMAN> CONNECT TARGET sys/oracle@JOHN;
    connected to target database: JOHN (DBID=1575580406)
    RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
    Until this you did correct. now just in a run block, like
    eg
    run
    allocate channel ....
    allocate channel...
    duplicate target database for standby from active database;

  • Ora-1276 cannot add controlfile - rman duplicate asm database

    Hi,
    I am trying to duplicate an asm database olddb -> asm database dup in the same diskgroup. somehow got error 0ra-1276 Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.
    There is nothing in the asm directory +DISK1/dup/controllfile before I run the rman.
    in the initdup.ora
    control_files=+DISK1,+DISK1 <--- just the disk group, not the file name
    db_name='dup'
    db_file_name_convert=+DISK1,+DISK1/dup
    log_file_name_convert=+DISK1,+DISK1
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Jun 18 20:58:06 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN> connect target sys/oracle@OLDDB
    connect auconnected to target database: OLDDB (DBID=1142960293)
    RMAN> xiliary /
    connected to auxiliary database: DUP (not mounted)
    RMAN> duplicate target database to dup
    logfile group 1 ('+DISK1/dup') size 200k ,
    group 2 ('+DISK1') size 200k;
    2> 3>
    Starting Duplicate Db at 2011/06/18 20:58:39
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=153 devtype=DISK
    WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
    contents of Memory Script:
    set until scn 1613638;
    set newname for datafile 1 to
    "+DISK1";
    set newname for datafile 2 to
    "+DISK1";
    set newname for datafile 3 to
    "+DISK1";
    set newname for datafile 4 to
    "+DISK1";
    set newname for datafile 6 to
    "+DISK1";
    restore
    check readonly
    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
    Starting restore at 2011/06/18 20:58:42
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to +DISK1
    restoring datafile 00002 to +DISK1
    restoring datafile 00003 to +DISK1
    restoring datafile 00004 to +DISK1
    restoring datafile 00006 to +DISK1
    channel ORA_AUX_DISK_1: reading from backup piece +DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731
    channel ORA_AUX_DISK_1: restored backup piece 1
    piece handle=+DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731 tag=TAG20110522T000530
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:06
    Finished restore at 2011/06/18 20:59:48
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUP" RESETLOGS ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1 ( '+DISK1/dup' ) SIZE 200 K ,
    GROUP 2 ( '+DISK1' ) SIZE 200 K
    DATAFILE
    '+DISK1/dup/datafile/system.1674.754174727'
    CHARACTER SET WE8ISO8859P1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/18/2011 20:59:48
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.
    RMAN>
    thank you very much for your help.
    thanks
    andrew

    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.Are you sure is it running under pfile?
    Ok, connect to auxiliary intance and post
    show parameter db_create
    show parameter control_filesIn your pfile, Have you mentioned single quotes?
    If your database with OMF then if you give it as below. as there is some work around
    Control_files='+DISK1/DUP/controlfile/control01.ctl','+DISK1/DUP/controlfile/control02.ctl'
    Check this too *Ora-1276 Error Recreating The Controlfile When Using +Asm [ID 303187.1]*

  • DUPLICATE DB : ORA-17629: Cannot connect to the remote database server

    [oracle@ora11g1 ~]$ export ORACLE_SID=sales
    [oracle@ora11g1 ~]$ rman target sys/sales@sales
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jun 5 13:00:15 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: SALES (DBID=690066655)
    RMAN> connect auxiliary sys/salestby2@salestby2
    connected to auxiliary database: SALES (not mounted)
    RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE SPFILE
    2> SET DB_NAME= 'sales'
    3> SET DB_UNIQUE_NAME= 'salestby2'
    4> SET control_files='/u02/oradata/salestby2/control01.ctl','/u02/oradata/salestby2/control02.ctl'
    5> SET DB_FILE_NAME_CONVERT='/u02/oradata/sales/','/u02/oradata/salestby2/'
    6> SET LOG_FILE_NAME_CONVERT='/u02/oradata/sales/','/u02/oradata/salestby2/';
    Starting Duplicate Db at 05-JUN-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=20 device type=DISK
    contents of Memory Script:
    backup as copy reuse
    targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwsales' auxiliary format
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwsalestby2' targetfile
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesales.ora' auxiliary format
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesalestby2.ora' ;
    sql clone "alter system set spfile= ''/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesalestby2.ora''";
    executing Memory Script
    Starting backup at 05-JUN-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=58 device type=DISK
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/05/2013 13:05:26
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-01017: invalid username/password; logon denied
    ORA-17629: Cannot connect to the remote database server
    continuing other job steps, job failed will not be re-run
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/05/2013 13:05:27
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/05/2013 13:05:27
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-01017: invalid username/password; logon denied
    ORA-17629: Cannot connect to the remote database server

    Welcome to the oracle forums!
    Please take some time to go through [url https://forums.oracle.com/forums/ann.jspa?annID=1535]FAQ PAGE
    Always post 4 digit oracle version and OS details.
    Post any query out put between \  \ tags
    Mark your questions as answered if you get the answer
    Password of SYS user on primary and standby must be same.Copy the password file from primary to standby server
    scp $ORACLE_HOME/dbs/orapwv112 <oracle_user@auxiliary_host>:/u01/app/oracle/product/11.2/dbs/orapwdupv112

  • ORA-01017 when RMAN duplicate from active database

    Hello, ORACLE guru's!
    I've got some trouble trying to duplicate DB via RMAN duplicate from active database.
    The script is simple:
    run
    allocate channel ch1 device type disk;
    allocate auxiliary channel aux1 device type disk;
    duplicate target database to mydb from active database;
    The problem is in this statement:
    Starting backup at 15-JAN-14
    channel ch1: starting datafile copy
    copying current control file
    Oracle instance started
    Total System Global Area   10689474560 bytes
    Fixed Size                     2237776 bytes
    Variable Size               4227861168 bytes
    Database Buffers            6442450944 bytes
    Redo Buffers                  16924672 bytes
    contents of Memory Script:
       sql clone "alter system set  db_name =
    ''mydb'' comment=
    ''Reset to original value by RMAN'' scope=spfile";
       sql clone "alter system reset  db_unique_name scope=spfile";
       shutdown clone immediate;
    executing Memory Script
    sql statement: alter system set  db_name =  ''mydb'' comment= ''Reset to original value by RMAN'' scope=spfile
    sql statement: alter system reset  db_unique_name scope=spfile
    Oracle instance shut down
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/15/2014 12:16:07
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ch1 channel at 01/15/2014 12:15:57
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-01017: invalid username/password; logon denied
    ORA-17629: Cannot connect to the remote database server
    RMAN>
    RMAN>

    change:
    export  ORACLE_SID="mydb"
    export ORACLE_HOME="/u/app/oracle/product/11.2/db_1"
    FILE1 = "/u/app/oracle/product/11.2/db_1/bin/"
    cat > $FILE1/sqlplus sys/karen as sysdba << EOF
    startup nomount; 
    exit;
    EOF
    cat > $FILE1/rman target sys/karen@mytargetdb auxiliary sys/karen@mydb << EOF
    run
    allocate channel ch1 device type disk;
    allocate auxiliary channel aux1 device type disk;
    duplicate target database to mydb from active database;
    EOF
    tell us if it works and again, from what host are you running the script?

  • DUPLICATE fails after recovery due to ORA-01861

    I issued the following duplicate command:
    DUPLICATE TARGET DATABASE TO dev2 UNTIL TIME '2006-09-16 04:30:00';It actually goes through the 8-hour task of restoring datafiles and recovering from archive logs. It then creates the control file and then executes the SET NEWNAME commands when it fails with this error
    executing command: SET NEWNAME
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/18/2006 08:17:07
    RMAN-03015: error occurred in stored script Memory Script
    ORA-01861: literal does not match format stringThe only possible cause I can think of is that, as of 16 Sep 2006, I hadn't yet set my NLS_DATE_FORMAT parameter. It is now set (to YYYY-MM-DD HH24:MI:SS) so that I can specify the date format for my PITR duplication.
    Does my diagnosis make any sense? If I unset NLS_DATE_FORMAT and say UNTIL TIME '16-SEP-06' does that mean '16-SEP-06 00:00:00'? That would work for me as well. However since each failed attempt means 8 hours lost I'd like to know that kind of thing ahead of time, and if my diagnosis is even correct.

    Normally we do have two senarios while cloning. One, you clone to an existing instance by removing the control and datafiles. Two, take a copy of spfile from target DB and clone to auxiliary DB. In the first case there can be chances that NLS is different than your target. But in second case it will be same because you are cloning from one parent setting.
    In your case if I am not wrong it was the first scenario ( This scenario I normally face in my UAT database clones when cloning from production). Its always better to keep same NLS but some situations u cant do that. In that case you can use “to_date” and it’s a very well proven method.
    And your question why your clone failed after all the restore operation. I personally think the database when tried to reset your logs after restoration it found format difference and shouted about that. As simple as that.

  • RMAN Active Cloning fails with RMAN-06054: missing log file

    Version Details:
    O.S Version     HP-UX B.11.31 U ia64
    Oracle DB Version     11.2.0.3.0
         Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Scenario :
    Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
    Problem:
    At the end of the cloning the below errors are reported;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2013 07:03:43
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 24751 and starting SCN of 89285945274
    RMAN Script used for Active cloning:
    #!/bin/ksh
    . setdb entDBu
    start_dt=`date +%Y%m%d_%H%M`
    job=`basename $0 ".sh"`
    rman  >> ${job}_${start_dt}.log  2>&1 <<eof
    set echo on;
    connect target sys/@DCC&(_O@entDBp1
    connect auxiliary sys/@DCC&(_O@entDBuu
    run {
    allocate channel prmy1 type disk;
    allocate auxiliary channel stby1 type disk;
    duplicate target database
    to entDBu
    from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
    show all;
    exit
    eof
    end_dt=`date +%Y%m%d_%H%M`
    mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
    started: ${start_dt}
    finish: ${end_dt}
    eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.

    Sivaprasad S wrote:
    Version Details:
    O.S Version     HP-UX B.11.31 U ia64
    Oracle DB Version     11.2.0.3.0
         Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Scenario :
    Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
    Problem:
    At the end of the cloning the below errors are reported;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2013 07:03:43
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 24751 and starting SCN of 89285945274RMAN Script used for Active cloning:
    #!/bin/ksh
    . setdb entDBu
    start_dt=`date +%Y%m%d_%H%M`
    job=`basename $0 ".sh"`
    rman  >> ${job}_${start_dt}.log  2>&1 <<eof
    set echo on;
    connect target sys/@DCC&(_O@entDBp1
    connect auxiliary sys/@DCC&(_O@entDBuu
    run {
    allocate channel prmy1 type disk;
    allocate auxiliary channel stby1 type disk;
    duplicate target database
    to entDBu
    from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
    show all;
    exit
    eof
    end_dt=`date +%Y%m%d_%H%M`
    mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
    started: ${start_dt}
    finish: ${end_dt}
    eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.Where UNTIL clause in your script I didn't saw.
    Please try following RMAN script
    DUPLICATE TARGET DATABASE FOR STANDBY
      FROM ACTIVE DATABASE
    SPFILE
       SET "control_files"="/u01/app/oracle/oradata/stbdbcontrol01.ctl"
       SET "db_name"="prmdb"
       SET "db_unique_name"="stbdb"
       SET "db_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
       SET "log_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
       SET "db_recovery_file_dest"="/u01/app/oracle/fra"
       SET "diagnostic_dest"=/u01/app/oracle"
       SET "audit_file_dest"="/u01/app/oracle/admin/stbdb/adump"
    PASSWORD FILE
    NOFILENAMECHECK;
    {code}
    Please change parameters for your environment.
    Regards
    Mahir M. Quluzade                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

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

  • Error while duplicate database for standby

    Hello Guys,
    Both of my database are 10gR2 and Linux is the operating system.
    I am trying to create a standby database for my production database.
    I have matched the directory structure of primary and standby database and there is no conflict. Directory permissions are also set.
    After taking the rman backup from production database when i connect auxiliary database from production. I run this command to duplicate database and create standby database.
    rman
    set until sequence XXXX;
    duplicate target database for standby dorecover nofilenamecheck;
    I get this error:
    executing Memory Script
    executing command: SET until clause
    Starting restore at 04-JUN-11
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /tmp/backup_files/standby_control_1jme2far_1_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/04/2011 21:00:37
    RMAN-03015: error occurred in stored script Memory Script
    ORA-19870: error reading backup piece /tmp/backup_files/standby_control_1jme2far_1_1
    ORA-01565: error in identifying file '/u01/app/oracle/product/10.2.0/db_1/dbs/spfileORCL.ora'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    */tmp/backup_files/standby_control_1jme2far_1_1 file exists*
    * spfileORCL.ora* exists on both servers in same directory and same path.
    Can you please suggest where is the problem?
    Thank you so much.
    Imran

    ORA-19870: error reading backup piece /tmp/backup_files/standby_control_1jme2far_1_1
    ORA-01565: error in identifying file '/u01/app/oracle/product/10.2.0/db_1/dbs/spfileORCL.ora'
    ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directory
    Might the backup piece not exist or file is unae to read at this time. Can you check is this physically exist Or not?
    And preferred to take new fresh backup and perform duplicate

Maybe you are looking for