RMAN Duplicate DB fails to restore datafile created during backup.

Database is 9i.
Performing duplicate database using rman on seperate host.
Reason of failure is , there were datafiles created during backup. Question is , Is there a workaround to perform duplicate database to work.
Error :
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/16/2007 14:42:44
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 791 found to restore
RMAN-06023: no backup or copy of datafile 790 found to restore
RMAN-06023: no backup or copy of datafile 789 found to restore
RMAN-06023: no backup or copy of datafile 788 found to restore
RMAN-06023: no backup or copy of datafile 787 found to restore
RMAN-06023: no backup or copy of datafile 786 found to restore
Backup Date is : 23rd Nov to 26th Nov
Datafile created between backup period are :
786 /oracle/prod/proddata17/btabd_322/btabd.data322 Nov-25-2007 02:58:38 AM
787 /oracle/prod/proddata17/btabd_323/btabd.data323 Nov-25-2007 03:06:02 AM
788 /oracle/prod/proddata17/btabd_324/btabd.data324 Nov-25-2007 03:17:48 AM
789 /oracle/prod/proddata17/btabd_325/btabd.data325 Nov-25-2007 03:26:50 AM
790 /oracle/prod/proddata17/btabd_326/btabd.data326 Nov-25-2007 03:32:31 AM
791 /oracle/prod/proddata17/btabd_327/btabd.data327 Nov-25-2007 03:39:59 AM
Restore Script :
rman TARGET dtbackup/dt0dmin@prod CATALOG rman_prd/rman_prd@rcat_db connect auxiliary /
run {
set until time = "TO_DATE('11/26/2007 10:30:00','mm/dd/yyyy hh24:mi:ss')";
allocate auxiliary channel aux1 type 'SBT_TAPE' PARMS="BLKSIZE=262144";
DUPLICATE TARGET DATABASE TO DUP ;
}

I think there is no workaround and this is expected behavior - atleast till 10.2. If you refer oracle documentation, it says that it requires target database in either MOUNT or OPEN stage to duplicate database using RMAN. So RMAN will get current physical structure information about target database from its control file and when any file is not there in the backup, it will give error. Only way to resolve this is to take backup of these datafiles through RMAN either as backupset or copy. ( I think oracle can take hint from here and make RMAN database duplication possible for which backup is not available - its a small change in code - if backup not found, then start taking backup. Already in 11g, during RMAN duplication, RMAN can use backup from other server)

Similar Messages

  • The RMAN Duplicate Command Fails During The Recover.

    This exact script works fine in our lab. We are using Oracle 10.2.0.4.0.
    The hot backup for standby is also a script which runs without error in both the lab and
    the production machine.
    I am obviously missing something.
    Any help would be greatly appreciated.
    Thanks,
    Jeff
    =================
    RMAN BACKUP SCRIPT
    =================
    RMAN> run
    2> {
    3> allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
    4> backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
    5> backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
    6> backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
    7> release channel c1;
    8> }
    released channel: ORA_DISK_1
    allocated channel: c1
    channel c1: sid=578 devtype=DISK
    Starting backup at 22-JAN-13
    channel c1: starting full datafile backupset
    channel c1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_05o02f01_1_1 tag=TAG20130122T144104 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:02
    Finished backup at 22-JAN-13
    Starting backup at 22-JAN-13
    channel c1: starting compressed full datafile backupset
    channel c1: specifying datafile(s) in backupset
    input datafile fno=00004 name=/u01/oradata/apoint/users01.dbf
    input datafile fno=00001 name=/u01/oradata/apoint/system01.dbf
    input datafile fno=00002 name=/u01/oradata/apoint/undotbs01.dbf
    input datafile fno=00003 name=/u01/oradata/apoint/sysaux01.dbf
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_06o02f05_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
    channel c1: backup set complete, elapsed time: 00:22:35
    channel c1: starting compressed full datafile backupset
    channel c1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_07o02gah_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:07
    Finished backup at 22-JAN-13
    Starting backup at 22-JAN-13
    current log archived
    channel c1: starting archive log backupset
    channel c1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=463 recid=5 stamp=805323439
    input archive log thread=1 sequence=464 recid=6 stamp=805331764
    input archive log thread=1 sequence=465 recid=7 stamp=805387242
    input archive log thread=1 sequence=466 recid=8 stamp=805387245
    input archive log thread=1 sequence=467 recid=9 stamp=805388633
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_08o02gaq_1_1 tag=TAG20130122T150354 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:36
    Finished backup at 22-JAN-13
    released channel: c1
    RMAN> exit
    Recovery Manager complete.
    =====================
    RMAN DUPLICATE SCRIPT
    =====================
    RMAN> run
    2> {
    3> allocate auxiliary channel c1 device type disk;
    4>
    5> duplicate target database for standby dorecover nofilenamecheck;
    6> release channel c1;
    7> }
    allocated channel: c1
    channel c1: sid=299 devtype=DISK
    Starting Duplicate Db at 21-JAN-13
    contents of Memory Script:
    set until scn 143395851;
    restore clone standby controlfile;
    sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 21-JAN-13
    channel c1: starting datafile backupset restore
    channel c1: restoring control file
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1 tag=1NETCMN1_6874_BK4STDBY
    channel c1: restore complete, elapsed time: 00:00:04
    output filename=/u01/oradata/apoint/control01.ctl
    output filename=/u02/oradata/apoint/control02.ctl
    output filename=/u03/oradata/apoint/control03.ctl
    Finished restore at 21-JAN-13
    sql statement: alter database mount standby database
    contents of Memory Script:
    set until scn 143395851;
    set newname for tempfile 1 to
    "/u01/oradata/apoint/temp01.dbf";
    switch clone tempfile all;
    set newname for datafile 1 to
    "/u01/oradata/apoint/system01.dbf";
    set newname for datafile 2 to
    "/u01/oradata/apoint/undotbs01.dbf";
    set newname for datafile 3 to
    "/u01/oradata/apoint/sysaux01.dbf";
    set newname for datafile 4 to
    "/u01/oradata/apoint/users01.dbf";
    restore
    check readonly
    clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    renamed temporary file 1 to /u01/oradata/apoint/temp01.dbf in control file
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 21-JAN-13
    channel c1: starting datafile backupset restore
    channel c1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/oradata/apoint/system01.dbf
    restoring datafile 00002 to /u01/oradata/apoint/undotbs01.dbf
    restoring datafile 00003 to /u01/oradata/apoint/sysaux01.dbf
    restoring datafile 00004 to /u01/oradata/apoint/users01.dbf
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1 tag=1NETCMN1_6874_BK4STDBY
    channel c1: restore complete, elapsed time: 00:21:32
    Finished restore at 21-JAN-13
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy recid=5 stamp=805323205 filename=/u01/oradata/apoint/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy recid=6 stamp=805323205 filename=/u01/oradata/apoint/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=7 stamp=805323206 filename=/u01/oradata/apoint/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=8 stamp=805323206 filename=/u01/oradata/apoint/users01.dbf
    contents of Memory Script:
    set until scn 143395851;
    recover
    standby
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 21-JAN-13
    starting media recovery
    channel c1: starting archive log restore to default destination
    channel c1: restoring archive log
    archive log thread=1 sequence=462
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1 tag=TAG20130121T183822
    channel c1: restore complete, elapsed time: 00:00:03
    archive log filename=/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch thread=1 sequence=462
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/oradata/apoint/system01.dbf'
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/21/2013 20:53:44
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch'
    ORA-16145: archival for thread# 1 sequence# 462 in progress
    RMAN> exit

    Jeff;
    I think the issue is in your backup. If you compare your command with mine, you may or may not see the issue, but this is how I got this to work.
    Yours
    RMAN run
    allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
    backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
    backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
    backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
    release channel c1;
    Mine
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
    release channel d1;
    }Your duplicate is very close to what I use :
    Yours
    RMAN> run
    allocate auxiliary channel c1 device type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel c1;
    Mine
    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    }Short notes :
    http://www.visi.com/~mseberg/duprman.html
    Best Regards
    mseberg

  • Duplicate Admin accounts on restoring from Time Machine backup

    I need help to remove duplicate accounts, created after restore from Time Machine Backup.
    Here is the situation:
    1. I was running SL on a Mac Pro with Time Machine backup. I had 5 User Accounts on the Login Window: Shared (Admin account), Dear Wife (DW, also Admin), Kid1 (managed), Kid2 (managed) and Guest (standard), and two 750 GB hard drives, HD1 and HD2.
    2. Mac Pro would not boot past the Apple logo with spinning icon.
    3. After talking to with Apple Support, it turned out that HD1 had crashed. I took it in to the Genius Bar, where they checked and confirmed HD1 crash and took it in for repair.
    4. Apple replaced HD1 and reinstalled SL.
    5. I picked up the Mac Pro. At home I reconnected TM and restarted.
    6. Upon restart, I clicked on restore from TM backup and there was only 1 TM backup visible to select. After several hours of Transferring Information, about 700 GB was restored
    7. Upon finishing restore, I saw the same Login Window as before crash, with the same 5 accounts - Shared, DW, Kid1, Kid2, Guest.
    8. Issue: From the Login Window, logging into Shared and clicking on HD1>Users, I now see: Home Icon with Shared1, and four additional folders: Shared, DW, Kid1, Kid2
    It seems I now have duplicate Shared accounts in the User folder - Shared1 with the Home icon, and a separate folder with name Shared.
    I cannot "Move to Trash" Shared, since I get the message: “Shared” can’t be modified or deleted because it’s required by Mac OS X.
    When I go into System Prefs>Accounts: I see My Account: Shared, and Other Accounts: DW, Kid1, Kid2, Guest. After unlocking the accounts, and right clicking on Shared for Advanced Options, I see:
    User: "Shared"
    -- Account Name: shared
    -- Home Directory:/Users/shared1
    Question: How do I consolidate or get rid of the duplicate Shared/Shared1 account? I have 350 GB of video/pictures/music in each of these accounts, which is unnecessarily eating up the new HD1.
    Any advice would be appreciated. Thanks!

    I solved the duplicate account problem.
    I had used Setup Assistant to restore from TM Backup and that gave me the duplicate accounts, i.e., method used was:
    http://web.me.com/pondini/Time_Machine/19.html
    After carefully reading Pondini's FAQs, I instead used the Restore and install Method, i.e.,
    http://web.me.com/pondini/Time_Machine/14.html
    No duplicate accounts anymore, problem solved.

  • Restore datafile without any Backup

    Hi,
    IBM AIX
    Oracle 10.2.0
    We have a problem in our database.
    One of our datafile was missing in the location.
    Database is in open mode. We dont have any backup of that physical file.
    Is there anyway to restore that datafile without backup.
    Plz Advice.....
    TIA,

    what is this file is it datafile or archive log file ..'/oracle/u01/app/oracle/oracle/product/10.2.0/db_1/logarchive/7603_1_594490386.dbf'.
    Can you check if this file is physically present.
    If its archive log file and not present physically do this
    When the recovery process suggests the non-existent archive log,you need to provide the path to the current online redo log. The current
    log can be determined from the following query:
    SELECT MEMBER
    FROM V$LOGFILE F,
    V$LOG L
    WHERE L.STATUS = 'CURRENT'
    AND L.GROUP# = F.GROUP#;
    Once you know the current log, restart the recovery procedure and provide the
    path to the log when prompted:
    yeah juct check the date after Enrique's comment When the recovery process suggests the non-existent archive log,
    you need to provide the path to the current online redo log. The current
    log can be determined from the following query:
    SELECT MEMBER
    FROM V$LOGFILE F,
    V$LOG L
    WHERE L.STATUS = 'CURRENT'
    AND L.GROUP# = F.GROUP#;
    Once you know the current log, restart the recovery procedure and provide the
    path to the log when prompted:
    Just check the date after Enrique;s comments
    Edited by: user445775 on Nov 1, 2008 9:43 AM

  • I am trying to restore files created using Backup in Tiger.  How do I do this on a Snow Leopard machine which is connected to the Tiger external drive?

    I have an external disk that was used on Tiger iMac. I used Backup to save files. Now that I have this external drive connected to a new IMac running SnowLeopard, how do I restore files?

    Backup 3.2 is still usable if you have a MM account and can download the upgrade.  Otherwise you'll need to restore them via Tiger.
    If the backup is not archived, then the individual files may be accessible directly.

  • Reading contents of .bin file created during backup function

    I have a backup .bin file that I made with the online function on the Linksys WRT54GS router. The router failed and I replaced it with a WRT54G2 router and I can't load he .bin file from the GS into the G2. Is there a way to read the contents of the .bin file so I can put the parameters from the old router into the new one?

    Probably not...the .bin file is an encrypted binary format (designed for security as there are router and wireless authentication passwords stored in it....
    Tomato 1.25vpn3.4 (SgtPepperKSU MOD) on a Buffalo WHR-HP-G54
    D-Link DSM-320 (Wired)
    Wii (Wireless) - PS3 (Wired), PSP (Wireless) - XBox360 (Wired)
    SonyBDP-S360 (Wired)
    Linksys NSLU2 Firmware Unslung 6.10 Beta unslung to a 2Gb thumb, w/1 Maxtor OneTouch III 200Gb
    IOmega StorCenter ix2 1TB NAS
    Linksys WVC54G w/FW V2.12EU
    and assorted wired and wireless PCs and laptops

  • RMAN duplicate failed

    Hi all,
    have below doubts.
    IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.
    Do I start from the beginning again or is there anyway to sort of "resume" from where it stopped?
    Please consider what need to do in 9i or in 10G.
    Please also reply what need to do for FS or for ASM.
    Please also share if you have any doc or link.

    Hi,
    IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.See always perform fresh duplicate.
    it will overwrite the existing files... so you need to check in alert log file like how many files restored & recovered during duplicate..
    sybrand_b wrote:
    Duplicate database is a quite robust command.
    It will automatically skip what has already been done, so you can safely re-execute it without problems.
    Been there, done that.
    Sybrand Bakker
    Senior Oracle DBA@sybrand
    What it automatically skips?
    1)did RMAN duplicate knows about earlier restores...
    2)if i restored system,sysaux,users,undo datafiles of another database and again I'm performing another database in same location.. so it will skip?
    are you sure...
    Thanks
    *Manual Completion of a Failed RMAN Duplicate [ID 360962.1]*
    Edited by: CKPT on Dec 11, 2010 12:40 PM

  • Rman duplicate database from test to production different host

    Dear All,
    usually i do the rman duplicate (clone) database in different host using same backup location as the source database in target database.
    now i am in situation to clone the database with different backup location
    source database location:/u01/db/backup
    target database location: /tmp_dbbkup
    is it possible to create the duplicate database with the command
    rman target sys@UAT1 auxiliary /
    RMAN>CATALOG BACKUPPIECE '/tmp_dbbkup/UAT_2670198561_44_20110101;
    RMAN>duplicate target database to DEV;
    is it ok?
    we dont have privilege/rights to create a folder/directory in production server.
    what i have to do now?
    thanks in advance.
    my oracle version: 10.2.0.4.0
    operating system: AIX

    tychos wrote:
    Hi rajeysh,
    what i have to do now?You could make a sym link on the dev server
    So /u01/db/backup on the dev server points to /tmp_dbbkup
    Regards,
    Tychothank for your reply tychos,
    $ ln -s /u01/db/backup/OUAT_2670198561_44_20110101 /oracle/db/backup/UAT_2670198561_44_20110101
    $ ls -ltr
    total 1475968
    -rw-r----- 1 oracle dba 307654656 Jan 7 10:03 db_DEV_20110107_4em1gm3e_1_1_L0
    -rw-r----- 1 oracle dba 448030720 Jan 7 10:03 db_DEV_20110107_4dm1gm3e_1_1_L0
    lrwxrwxrwx 1 oracle dba 45 Jan 11 20:53 UAT_2670198561_44_20110101 -> /u01/db/backup/OUAT_2670198561_44_20110101
    $ ln -s /u01/db/backup/AOUAT_2670198561_46_20110101 /oracle/db/backup/OUAT_2670198561_46_20110101
    $ ln -s /u01/db/backup/OUAT_2670198561_47_20110101 /oracle/db/backup/OUAT_2670198561_47_20110101
    $ ln -s /u01/db/backup/OUAT_2670198561_45_20110101 /oracle/db/backup/OUAT_2670198561_45_20110101
    $
    is it ok
    will the duplicate gets the information from /oracle/db/backup
    if i did anything wrong , please correct me?

  • Rman restore from last week backup

    Hi guys
    i need to restore last week rman backup from .. we are not using catalog database.
    i need to restore it on same machine with diff mount point ..
    i know i can use tag option of restore specifically last week backup but its production restore so thought if anybody can give me list of steps i need to follow .. anybody who has done this before.
    do i have to fire resetlogs at the end as its incomplete recovery .. i need last saturday backup .. don't want monday backup on top of it.
    please help me in this.
    Regards

    You have to ensure that your controlfile, redo log file and database file locations are different from your production database.
    Ensure that your instance parameter file specifies a different location for control_files
    Use db_file_name_convert -- however, I prefer to explicitly name a new location for each datafile, in case your database files are spread across multiple directories and you miss one or more in db_file_name_convert. (you don't want RMAN to restore datafiles from the backup to the current locations and overwrite your production database files !)
    Hemant K Chitale
    http://hemantoracledba.blogspot.com
    Edited by: Hemant K Chitale on Apr 22, 2010 6:06 PM

  • ORA-01180: can not create datafile 1 during RMAN restore.

    Hello,
    I am trying to refresh one of our QA environments and I am getting this error message:
    RMAN> run
    2> {
    3> allocate channel c1 device type disk;
    4> allocate channel c2 device type disk;
    5> restore database;
    6> recover database;
    7> }
    allocated channel: c1
    channel c1: SID=5 device type=DISK
    allocated channel: c2
    channel c2: SID=131 device type=DISK
    Starting restore at 08-NOV-12
    using channel ORA_DISK_1
    creating datafile file number=1 name=+DATA1/alephpr/datafile/system.269.722874729
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/08/2012 16:27:40
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DATA1/alephpr/datafile/system.269.722874729' I created a new database from scratch with the same name as is in Production, later on I will proceed to rename it to the right one. I started the steps for refreshing the PRD copy:
    RMAN> shutdown immediate
    using target database control file instead of recovery catalog
    database dismounted
    Oracle instance shut down
    RMAN> startup nomount
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 534462464 bytes
    Fixed Size 2228200 bytes
    Variable Size 176160792 bytes
    Database Buffers 348127232 bytes
    Redo Buffers 7946240 bytes
    RMAN> set dbid=3573460394
    executing command: SET DBID
    RMAN> restore controlfile from '/restorealeph/c-3573460394-20121106-01';
    Starting restore at 08-NOV-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=130 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
    +output file name=+DATA1/alephpr/controlfile/current.260.798747585+
    +output file name=+FLASH/alephpr/controlfile/current.276.798747585+
    Finished restore at 08-NOV-12
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1Once the control file is restored, I need to crosscheck, delete expired and catalog the backups at the new server:
    RMAN> crosscheck backup;
    Crosschecked 48 objects
    RMAN> delete noprompt expired backup;
    Deleted 48 EXPIRED objects
    RMAN> list backup summary;
    specification does not match any backup in the repositoryI need now to catalog the backups we transferred from Prod into the QA server's directory /restorealeph:
    RMAN> catalog start with '/restorealeph/';
    searching for all files that match the pattern /restorealeph/
    List of Files Unknown to the Database
    =====================================
    File Name: /restorealeph/9cnpm51u_1_1
    File Name: /restorealeph/9enpm6lj_1_1
    File Name: /restorealeph/c-3573460394-20121107-00
    File Name: /restorealeph/c-3573460394-20121107-01
    File Name: /restorealeph/c-3573460394-20121106-01
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /restorealeph/9cnpm51u_1_1
    File Name: /restorealeph/9enpm6lj_1_1
    File Name: /restorealeph/c-3573460394-20121107-00
    File Name: /restorealeph/c-3573460394-20121107-01
    File Name: /restorealeph/c-3573460394-20121106-01
    RMAN> list backup summary;
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    4097    B  F  A DISK        07-NOV-12       1       1       NO         BACKUP_ALEPHPR.TUR_110712030000
    4098    B  A  A DISK        07-NOV-12       1       1       NO         BACKUP_ALEPHPR.TUR_110712030000
    RMAN> list backup tag="BACKUP_ALEPHPR.TUR_110712030000";
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    4097    Full    178.04G    DISK        00:00:00     07-NOV-12
            BP Key: 4097   Status: AVAILABLE  Compressed: NO  Tag: BACKUP_ALEPHPR.TUR_110712030000
            Piece Name: /restorealeph/9cnpm51u_1_1
      List of Datafiles in backup set 4097
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/system.269.722874729
      2       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/sysaux.266.722874731
      3       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.289.722874727
      4       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.257.722874727
      5       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/users.298.722874731
      6       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/audit.299.723372305
      7       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_datos.260.723372307
      8       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_indices.261.723372307
      9       Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_hist.262.723372309
      10      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_l.264.723372319
      11      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_long.265.723372349
      12      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_md.270.723372355
      13      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.271.723372369
      14      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_xl.272.723372375
      15      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_l.273.723372401
      16      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_md.274.723372427
      17      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_sm.275.723372455
      18      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_xl.276.723372473
      19      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/tools.278.723372501
      26      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.300.736088959
      27      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_meta.301.746385117
      28      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_pstore.302.746385119
      29      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_cache.304.746385121
      30      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.305.796391931
      31      Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.306.796392185
    BS Key  Size       Device Type Elapsed Time Completion Time
    4098    16.89G     DISK        00:00:00     07-NOV-12
            BP Key: 4098   Status: AVAILABLE  Compressed: NO  Tag: BACKUP_ALEPHPR.TUR_110712030000
            Piece Name: /restorealeph/9enpm6lj_1_1
      List of Archived Logs in backup set 4098
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      1    35722   6919870864350 06-NOV-12 6919871887697 06-NOV-12
      1    35723   6919871887697 06-NOV-12 6919872372211 06-NOV-12
      1    35724   6919872372211 06-NOV-12 6919872410158 06-NOV-12
      1    35725   6919872410158 06-NOV-12 6919872447301 06-NOV-12
      1    35726   6919872447301 06-NOV-12 6919872503332 06-NOV-12
      1    35727   6919872503332 06-NOV-12 6919872551564 06-NOV-12
      1    35728   6919872551564 06-NOV-12 6919872603881 06-NOV-12
      1    35729   6919872603881 06-NOV-12 6919872655942 06-NOV-12
      1    35730   6919872655942 06-NOV-12 6919872698722 06-NOV-12
      1    35731   6919872698722 06-NOV-12 6919872741655 06-NOV-12
      1    35732   6919872741655 06-NOV-12 6919872782284 06-NOV-12
      1    35733   6919872782284 06-NOV-12 6919872872302 06-NOV-12
      1    35734   6919872872302 06-NOV-12 6919872910206 06-NOV-12
      1    35735   6919872910206 06-NOV-12 6919872945577 06-NOV-12
      1    35736   6919872945577 06-NOV-12 6919872980056 06-NOV-12
      1    35737   6919872980056 06-NOV-12 6919873013411 06-NOV-12
      1    35738   6919873013411 06-NOV-12 6919873050761 06-NOV-12
      1    35739   6919873050761 06-NOV-12 6919873084996 06-NOV-12
      1    35740   6919873084996 06-NOV-12 6919873122049 06-NOV-12
      1    35741   6919873122049 06-NOV-12 6919873521767 06-NOV-12
      1    35742   6919873521767 06-NOV-12 6919873952773 06-NOV-12
      1    35743   6919873952773 06-NOV-12 6919874258549 06-NOV-12
      1    35744   6919874258549 06-NOV-12 6919874472213 06-NOV-12
      1    35745   6919874472213 06-NOV-12 6919874744856 06-NOV-12
      1    35746   6919874744856 06-NOV-12 6919875113086 06-NOV-12
      1    35747   6919875113086 06-NOV-12 6919875733337 06-NOV-12
      1    35748   6919875733337 06-NOV-12 6919876139061 06-NOV-12
      1    35749   6919876139061 06-NOV-12 6919876707162 06-NOV-12
      1    35750   6919876707162 06-NOV-12 6919877706313 06-NOV-12
      1    35751   6919877706313 06-NOV-12 6919877919039 06-NOV-12
      1    35752   6919877919039 06-NOV-12 6919878024429 06-NOV-12
      1    35753   6919878024429 06-NOV-12 6919878107673 06-NOV-12
      1    35754   6919878107673 06-NOV-12 6919878258511 06-NOV-12
      1    35755   6919878258511 06-NOV-12 6919878308336 06-NOV-12
      1    35756   6919878308336 06-NOV-12 6919878424419 06-NOV-12
      1    35757   6919878424419 06-NOV-12 6919878488485 06-NOV-12
      1    35758   6919878488485 06-NOV-12 6919878827092 06-NOV-12
      1    35759   6919878827092 06-NOV-12 6919879350098 07-NOV-12
      1    35760   6919879350098 07-NOV-12 6919879675556 07-NOV-12
      2    35949   6919870864360 06-NOV-12 6919871494640 06-NOV-12
      2    35950   6919871494640 06-NOV-12 6919871887487 06-NOV-12
      2    35951   6919871887487 06-NOV-12 6919872410655 06-NOV-12
      2    35952   6919872410655 06-NOV-12 6919872552468 06-NOV-12
      2    35953   6919872552468 06-NOV-12 6919872698940 06-NOV-12
      2    35954   6919872698940 06-NOV-12 6919872872690 06-NOV-12
      2    35955   6919872872690 06-NOV-12 6919872980371 06-NOV-12
      2    35956   6919872980371 06-NOV-12 6919873085902 06-NOV-12
      2    35957   6919873085902 06-NOV-12 6919873569082 06-NOV-12
      2    35958   6919873569082 06-NOV-12 6919873949096 06-NOV-12
      2    35959   6919873949096 06-NOV-12 6919874404640 06-NOV-12
      2    35960   6919874404640 06-NOV-12 6919875011814 06-NOV-12
      2    35961   6919875011814 06-NOV-12 6919875631429 06-NOV-12
      2    35962   6919875631429 06-NOV-12 6919876324885 06-NOV-12
      2    35963   6919876324885 06-NOV-12 6919876363526 06-NOV-12
      2    35964   6919876363526 06-NOV-12 6919876748508 06-NOV-12
      2    35965   6919876748508 06-NOV-12 6919877741784 06-NOV-12
      2    35966   6919877741784 06-NOV-12 6919878108943 06-NOV-12
      2    35967   6919878108943 06-NOV-12 6919878424477 06-NOV-12
      2    35968   6919878424477 06-NOV-12 6919879012111 06-NOV-12
      2    35969   6919879012111 06-NOV-12 6919879260589 07-NOV-12
      2    35970   6919879260589 07-NOV-12 6919879350086 07-NOV-12
      2    35971   6919879350086 07-NOV-12 6919879464935 07-NOV-12
      2    35972   6919879464935 07-NOV-12 6919879548399 07-NOV-12
      2    35973   6919879548399 07-NOV-12 6919879675564 07-NOV-12
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1       1       ALEPHPR  3573460394       PARENT  1          13-MAY-10
    2       2       ALEPHPR  3573460394       PARENT  2229467    28-JUN-10
    3       3       ALEPHPR  3573460394       CURRENT 6918261828355 26-SEP-12The ASM structure is created...
    ASMCMD> lsdg
    State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
    MOUNTED EXTERN N 512 4096 1048576 509282 507421 0 507421 0 N DATA1/
    MOUNTED EXTERN N 512 4096 1048576 50641 42850 0 42850 0 N FLASH/
    ASMCMD> cd DATA1/ALEPHPR/DATAFILE
    ASMCMD> pwd
    +DATA1/ALEPHPR/DATAFILEBoth source and target databases are 11.2.0.2 PSU 6 running on Linux x64. I cannot use RMAN Duplicate since there is no visibility among different environments (PROD - QA in this case).
    Any idea?
    Thanks
    Martin
    Edited by: martin.morono on Nov 8, 2012 11:19 AM
    Edited by: martin.morono on Nov 8, 2012 11:49 AM

    Thanks Levi,
    I slightly modified your script to recatalog the backup pieces since they are note stored at the same location in PR and QA.
    No luck. The error message is different but the result is the same... it keeps failing.
    RMAN> run {
    2> allocate channel c1 device type disk;
    3> allocate channel c2 device type disk;
    4> restore controlfile from '/restorealeph/c-3573460394-20121107-01';
    5> startup mount;
    6> catalog start with '/restorealeph/';
    7> restore database from tag 'BACKUP_ALEPHPR.TUR_110712030000';
    8> }
    allocated channel: c1
    channel c1: SID=191 device type=DISK
    allocated channel: c2
    channel c2: SID=131 device type=DISK
    Starting restore at 09 NOV 2012 13:11:09
    channel c2: skipped, AUTOBACKUP already found
    channel c1: restoring control file
    channel c1: restore complete, elapsed time: 00:00:15
    output file name=+DATA1/alephpr/controlfile/current.260.798747585
    output file name=+FLASH/alephpr/controlfile/current.276.798747585
    Finished restore at 09 NOV 2012 13:11:24
    database is already started
    database mounted
    Starting implicit crosscheck backup at 09 NOV 2012 13:11:31
    Crosschecked 52 objects
    Finished implicit crosscheck backup at 09 NOV 2012 13:11:39
    Starting implicit crosscheck copy at 09 NOV 2012 13:11:39
    Crosschecked 2 objects
    Finished implicit crosscheck copy at 09 NOV 2012 13:11:40
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_1.279.795017193
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_34950.273.795014469
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_1.281.795017413
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_2.283.795017519
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_3.290.795018411
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_4.291.795018559
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_5.292.795018707
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_6.293.795018811
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_7.294.795018899
    File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_8.295.795020509
    File Name: +flash/ALEPHPR/CONTROLFILE/Current.268.798725123
    searching for all files that match the pattern /restorealeph/
    List of Files Unknown to the Database
    =====================================
    File Name: /restorealeph/9cnpm51u_1_1
    File Name: /restorealeph/9enpm6lj_1_1
    File Name: /restorealeph/c-3573460394-20121107-00
    File Name: /restorealeph/c-3573460394-20121107-01
    File Name: /restorealeph/c-3573460394-20121106-01
    Do you really want to catalog the above files (enter YES or NO)? YEs
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /restorealeph/9cnpm51u_1_1
    File Name: /restorealeph/9enpm6lj_1_1
    File Name: /restorealeph/c-3573460394-20121107-00
    File Name: /restorealeph/c-3573460394-20121107-01
    File Name: /restorealeph/c-3573460394-20121106-01
    Starting restore at 09 NOV 2012 13:11:48
    released channel: c1
    released channel: c2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/09/2012 13:11:48
    RMAN-06026: some targets not found - aborting 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 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>Just in case, I re-run this script including the crosscheck backup and the delete noprompt expired backups before restoring an the error messages were the same.
    THanks again for your help.
    Regards.
    Martin
    Edited by: martin.morono on Nov 9, 2012 7:21 AM

  • Cleaning up ASM disk group after failed rman duplicate session?

    I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
    I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
    Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
    So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
    Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
    Thanks.

    Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
    SQL> desc v$asm_file
    Name Null? Type
    GROUP_NUMBER NUMBER
    FILE_NUMBER NUMBER
    COMPOUND_INDEX NUMBER
    INCARNATION NUMBER
    BLOCK_SIZE NUMBER
    BLOCKS NUMBER
    BYTES NUMBER
    SPACE NUMBER
    TYPE VARCHAR2(64)
    REDUNDANCY VARCHAR2(6)
    STRIPED VARCHAR2(6)
    CREATION_DATE DATE
    MODIFICATION_DATE
    This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

  • Restore datafile problem (RMAN)

    I delete the datafile branch.
    Than restore it form the yesterdays backup
    RMAN>restore tablespace branch.
    successfully restored branch.dbf.
    RMAN> recover tablespace branch;
    archive log thread 1 sequence 12 is already on disk as file C:\ESAS\ORACLE\APP\O
    RACLE\FLASH_RECOVERY_AREA\XE\ARCHIVELOG\2008_01_21\O1_MF_1_12_3S8KWFJM_.ARC
    archive log thread 1 sequence 13 is already on disk as file C:\ESAS\ORACLE\APP\O
    RACLE\FLASH_RECOVERY_AREA\XE\ARCHIVELOG\2008_01_21\O1_MF_1_13_3S8KWZM1_.ARC
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/21/2008 10:20:57
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 5 lowscn 28752248 found to restore
    RMAN-06025: no backup of log thread 1 seq 4 lowscn 28749190 found to restore
    RMAN-06025: no backup of log thread 1 seq 3 lowscn 28735538 found to restore
    RMAN-06025: no backup of log thread 1 seq 2 lowscn 28732630 found to restore
    RMAN-06025: no backup of log thread 1 seq 1 lowscn 28704663 found to restore
    RMAN-06025: no backup of log thread 1 seq 4 lowscn 28704627 found to restore
    RMAN-06025: no backup of log thread 1 seq 3 lowscn 28684595 found to restore
    RMAN-06025: no backup of log thread 1 seq 2 lowscn 28664563 found to restore
    RMAN-06025: no backup of log thread 1 seq 1 lowscn 28642042 found to restore
    RMAN-06025: no backup of log thread 1 seq 2225 lowscn 28640983 found to restore
    RMAN-06025: no backup of log thread 1 seq 2224 lowscn 28640978 found to restore
    RMAN-06025: no backup of log thread 1 seq 2223 lowscn 28633884 found to restore
    SQL> alter tablespace branch online;
    alter tablespace branch online
    ERROR at line 1:
    ORA-01190: control file or data file 4 is from before the last RESETLOGS
    ORA-01110: data file 4: 'C:\ESAS\ORACLE\ORADATA\XE\BRANCH.DBF'
    Also the size of the branch.dbf is 2,800GB normally, but when I restore it from the backupset it is nearly 500MB.

    If you did a RESETLOGS 3 days ago, that would have been between
    the SCNs 26840983 and 28642042 ! based on these lines :
    RMAN-06025: no backup of log thread 1 seq 1 lowscn 28642042 found to restore
    RMAN-06025: no backup of log thread 1 seq 2225 lowscn 28640983 found to restore
    However you do not expect to see a 500MB file. So I wonder if Oracle found
    no backup of the datafile from recent days but found the most recent backup to be of so long ago (3+ days) that the datafile then was only 500MB.
    That would mean that your recent daily backups have been failing or silently erroring out.
    If RMAN cannot find a most recent (eg yesterday's) backup of a datafile, it will go back in time till it can find the "lastest" backup -- so the "lastest" backup of that datafile was a 500MB image many days ago ?
    Check your backup destination directory -- your FlashbackRecoveryArea to see if backups are really going there. Check your backup logs.

  • Problems creating control file in RMAN duplicate database

    There is so much detail involved in this operation that I don't know what might be useful, so I'll start simple. I'm attempting to clone a database on the same host using RMAN "duplicate database". I finally got all the setup done, the OS authentication hurdles hurdled, etc. and entered the command:
    duplicate target database to COPYCH2M until time "to_date('March 15 2012 12:00:00', 'Mon DD YYYY HH24:MI:SS')";
    The first time I got:
    ORA-19504: failed to create file "/u01/app/oracle/oradata/COPYCH2M/control01.ctl"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 2: No such file or directory
    There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/21/2012 15:59:25
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 11.1.0.1.0
    ORA-00202: control file: '/u01/app/oracle/oradata/COPYCH2M/control01.ctl'
    Sounds straightforward, if frustrating, right? Apparently you can't duplicate a database that's not in the exact same version. But:
    1) The backuppiece we got the control file from was from last November.
    2) The version of Oracle has not been updated since that time.
    How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
    Thanks, I'm hoping this is easy but I can post more info if needed.

    >
    There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
    >
    The database is limited as to what it can create. Since you defined where you wanted the controlfiles to go (pfile/spfile), it's up to you to make sure the directory is valid and exists. :)
    >
    How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
    >
    As for your controlfiles, make sure the compatible parameter is set the same on both the source and the target unless you are using the default (11.1.0.1 for you, and you aren't)
    Keep going, you'll get there. RMAN duplicate is a great feature.
    Good luck.

  • RMAN -06100: no channel to restore a backup or copy of datafile 51

    Oracle 10.2.0.4
    I am attempting to duplicate a database from a full backup that was written to tape. I connect to a catalog, the target, and an auxilliary database. I allocate channels for disk and allocate auxiliary channels. For testing purposes I am trying to restore one data file from tape to disk but get RMAN-06100.
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 23 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/xxxxx/oracle/tivoli/ndk8oasu181.opt)';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/xxxx/oracle/product/1020/db_1/dbs/snapcf_prd002l.f'; # default
    RMAN> run
    2> { allocate channel d01 type disk;
    3> allocate channel d02 type disk;
    4> allocate channel d03 type disk;
    5> allocate channel d04 type disk;
    6> allocate channel d05 type disk;
    7> allocate auxiliary channel stby01 type disk;
    8> allocate auxiliary channel stby02 type disk;
    9> set newname for datafile '/xxxxxx/d01/oradata/prd002l/patdata01.dbf' to '/xxxxxx/d26/oradata/prd002lp/patdata01.dbf';
    10> restore datafile '/xxxxxx/d01/oradata/prd002l/patdata01.dbf';
    11> release channel ch01;
    12> release channel ch02;
    13> }
    starting full resync of recovery catalog
    full resync complete
    allocated channel: d01
    channel d01: sid=1859 devtype=DISK
    allocated channel: d02
    channel d02: sid=1825 devtype=DISK
    allocated channel: d03
    channel d03: sid=2252 devtype=DISK
    allocated channel: d04
    channel d04: sid=1978 devtype=DISK
    allocated channel: d05
    channel d05: sid=1906 devtype=DISK
    allocated channel: stby01
    channel stby01: sid=1406 devtype=DISK
    allocated channel: stby02
    channel stby02: sid=1462 devtype=DISK
    executing command: SET NEWNAME
    Starting restore at 12-MAY-11
    released channel: d01
    released channel: d02
    released channel: d03
    released channel: d04
    released channel: d05
    released channel: stby01
    released channel: stby02
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 05/12/2011 08:00:46
    RMAN-06026: some targets not found - aborting restore
    RMAN-06100: no channel to restore a backup or copy of datafile 51

    Here is some additional information:
    6100, 1, "no channel to restore a backup or copy of datafile %d"
    // *Cause: A datafile, tablespace, or database restore could not proceed
    // because the backup of the indicated file exists on a device type
    // that was not allocated for restore.
    // *Action: None - this is an informational message. See message 6026 for
    // further details.
    what do i need to do to correct this: backup of the indicated file exists on a device type that was not allocated for restore

  • RMAN-06085: must use SET NEWNAME command to restore datafile 'MISSING00'

    Tried to restore again but got this message.
    RMAN-06085: must use SET NEWNAME command to restore datafile /oracle/Ora11g/dbs/MISSING00126

    no, im not restoring datafile to different location.
    this is what i encounter after a successfull restore and but failed recover.
    My original post is on the other thread.
    i was just desperate to start a new thread since there are nobody but only one who replied
    Hope you could go to that thread and help me... topic: (Success on RESTORE but failed on RECOVER-- need help)
    thanks in advance...

Maybe you are looking for