Duplicate DBID

Hi all,
Just wondering what are the implication of having different DBNAME but same DBID of Production and Test Database.
regards,
Luckys

While considering what Mark is saying, you may be able to distinguish your connection via target but once connected, and then when you backup the database, the backupset info. along with all other relevant information will be stored based on the dbid in the repository. So when it's time to restore or recover the database, the repository won't be able to distinguish among the different databases (since they share the same dbid value)
Hope it's clear
Regards

Similar Messages

  • RMAN Backup and TSM

    We normally take L-0 Hot backups for Non Production once in 7 days. The keep occupying space in TSM.
    Once in 3 months our Non Production Databases undergo cloning from Production.The cloning happens via RMAN Duplicate.DBID changes.
    Once the clone is completed,we dont need the backups of the older DBID and we start taking L-0 backups of the newer DBID.
    How can we get rid of the non Production Backups in TSM for the older DBID. and reclaim space in TSM?

    Issue a DELETE BACKUP before you drop the database or clone it from production.
    Hemant K Chitale
    I had the same issue. For backups that I hadn't DELETEd before changing the DBID, the TSM adminsitrator manually purged the backups. However, we had to change the "filename" portion of the new DBID Tivoli backups else the purge would also purge new backups. TSM doesn't track backups by DBID but only by filename.
    Hemant K Chitale
    Edited by: Hemant K Chitale on May 23, 2013 9:39 AM
    Edited by: Hemant K Chitale on May 23, 2013 9:40 AM

  • Duplicate target database not working

    Hi All,
    I want to clone my exisitng DB to other.
    I was refering the below link to do the same.
    [http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm|http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm]
    OS:Solaris 10
    Oracle version:10.2.0.4.0
    What I did tilll now:-
    1) Created a database MYDB1 in archive mode
    2) Created one tablespace, user and 1 table in DB
    3) Registered the MYDB1 in RMAN Db.
    4)Created a Pfile from MYDB1 database and changed db value and other values of MYDB1 to MYDB2(Database name to be duplicate)
    5)Created a password file
    6)Startup MYDB2 in NOMOUNT stage.
    7) At RMAN prompt I have done below things to but i have getting the error
    rman:rman:>rman target sys/mydb1@mydb1 catalog rman/rman auxiliary sys/mydb2@mydb2
    Recovery Manager: Release 10.2.0.4.0 - Production on Fri Sep 7 12:20:22 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: MYDB1 (DBID=3867673817)
    connected to recovery catalog database
    connected to auxiliary database: MYDB2 (not mounted)
    RMAN> DUPLICATE TARGET DATABASE TO mydb2;
    Starting Duplicate Db at 07-SEP-12
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=162 devtype=DISK
    WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
    contents of Memory Script:
       set until scn  911233;
       set newname for datafile  1 to
    "+disk2";
       set newname for datafile  2 to
    "+disk2";
       set newname for datafile  3 to
    "+disk2";
       set newname for datafile  4 to
    "+disk2";
       set newname for datafile  5 to
    "+disk2";
       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 07-SEP-12
    using channel ORA_AUX_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/07/2012 12:21:01
    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 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
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    745933  B  F  A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
    745934  B  F  A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
    RMAN> list backup of database;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    745933  Full    549.12M    DISK        00:01:19     07-SEP-12
            BP Key: 745935   Status: AVAILABLE  Compressed: NO  Tag: FULL_BACKUP
            Piece Name: /backup/oracle_backup/test_dir/rman_bkp/mydb1_0gnkjokf_1_1
      List of Datafiles in backup set 745933
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/system.256.793120373
      2       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/undotbs1.258.793120373
      3       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/sysaux.257.793120373
      4       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/users.259.793120373
      5       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/tbs_umesh.266.793207735
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup/oracle_backup/test_dir/rman_bkp/mydb1_%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/software/oracle/product/10.2.0/database/dbs/snapcf_mydb1.f'; # default
    RMAN> exit
    Recovery Manager complete.
    @rman:rman:>Please Suggest where i am going wrong..
    Regards
    Umesh Gupta

    WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
    You must check DB_FILE_NAME_CONVERT parameter on MYDB2 database
    or I think you must add DB_FILE_NAME_CONVERT, LOG_FILE_NAME_CONVERT to DUPLICATE Command.
    DUPLICATE TARGET DATABASE TO MYDB2
    SPFILE
    SET
      "DB_FILE_NAME_CONVERT"="+DATA/MYDB1/","+DATA/MYDB2"
    ...  Regards
    Mahir M. Quluzade
    www.mahir-quluzade.com

  • Error in creating Duplicate Database in same server..

    Hi,
    I am getting following error when creating duplicate database
    DB Version=10.2.0.4
    $ rman target sys/sys@test nocatalog auxiliary /
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 28 15:13:32 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: TEST (DBID=1702666620, not open)
    using target database control file instead of recovery catalog
    connected to auxiliary database: CLNTEST (not mounted)
    RMAN> DUPLICATE TARGET DATABASE TO "CLNTEST";
    Starting Duplicate Db at 28-SEP-09
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=156 devtype=DISK
    contents of Memory Script:
    set until scn 597629461;
    set newname for datafile 1 to
    "/u01/data_new/clonetest/system01.dbf";
    set newname for datafile 2 to
    "/u01/data_new/clonetest/undotbs01.dbf";
    set newname for datafile 3 to
    "/u01/data_new/clonetest/sysaux01.dbf";
    set newname for datafile 4 to
    "/u01/data_new/clonetest/users01.dbf";
    set newname for datafile 5 to
    "/u01/data_new/clonetest/example01.dbf";
    set newname for datafile 6 to
    "/u01/data_new/clonetest/undotbs02.dbf";
    set newname for datafile 7 to
    "/u01/data_new/clonetest/alweb1.dbf";
    set newname for datafile 8 to
    "/u01/data_new/clonetest/indx1.dbf";
    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
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 28-SEP-09
    using channel ORA_AUX_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/28/2009 15:13:40
    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 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> crosscheck backupset of datafile 1;
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=154 devtype=DISK
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 2;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 3;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 4;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 5;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 6;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    RMAN> crosscheck backupset of datafile 7;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u01/rmanbkp/db_prd0akqcnoh_1_1 recid=10 stamp=698769169
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u02/data/flash_recovery_area/BINGO/backupset/2009_09_28/o1_mf_nnndf_TAG20090928T151044_5d114x0h_.bkp recid=17 stamp=698771444
    Crosschecked 2 objects
    Thanks,

    Hi,
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/ora10g/product/10.2.0/db_1/dbs/snapcf_TEST.f'; # default
    Thanks,

  • Error during "duplicate target ... from active database"

    hi:
    RMAN duplicate failure after the auxiliary instance mounted,we want to create a physical standby database .
    Platform: solaris10 spark 64bit
    Version: 11.2.0.1.5 (both primary and standby)
    thank you..
    RMAN log:
    rman target sys/password@his_primary auxiliary sys/password@his_standby_tt
    Recovery Manager: Release 11.2.0.1.0 - Production on Thu Aug 30 15:40:06 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: HIS (DBID=3271178181)
    connected to auxiliary database: HIS (not mounted)
    RMAN> duplicate target database for standby from active database;
    Starting Duplicate Db at 30-AUG-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=2833 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=3399 device type=DISK
    allocated channel: ORA_AUX_DISK_3
    channel ORA_AUX_DISK_3: SID=3966 device type=DISK
    allocated channel: ORA_AUX_DISK_4
    channel ORA_AUX_DISK_4: SID=3 device type=DISK
    contents of Memory Script:
    backup as copy reuse
    targetfile '/u01/oracle/product/11.2.0/db_1/dbs/orapwhis' auxiliary format
    '/u01/app/oracle/product/11.2.0/db_1/dbs/orapwhis' ;
    executing Memory Script
    Starting backup at 30-AUG-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1570 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=1708 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=1851 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=1995 device type=DISK
    Finished backup at 30-AUG-12
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format '/u01/app/oradata/his/control01.ctl';
    restore clone controlfile to '/u01/app/oradata/his/control02.ctl' from
    '/u01/app/oradata/his/control01.ctl';
    restore clone controlfile to '/u01/app/oradata/his/control03.ctl' from
    '/u01/app/oradata/his/control01.ctl';
    executing Memory Script
    Starting backup at 30-AUG-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    channel ORA_DISK_1: starting datafile copy
    copying standby control file
    output file name=/export/home/oracle/snap.f tag=TAG20120830T154059 RECID=9 STAMP=792690060
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    Finished backup at 30-AUG-12
    Starting restore at 30-AUG-12
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    using channel ORA_AUX_DISK_3
    using channel ORA_AUX_DISK_4
    channel ORA_AUX_DISK_2: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_3: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_4: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_1: copied control file copy
    Finished restore at 30-AUG-12
    Starting restore at 30-AUG-12
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    using channel ORA_AUX_DISK_3
    using channel ORA_AUX_DISK_4
    channel ORA_AUX_DISK_2: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_3: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_4: skipped, AUTOBACKUP already found
    channel ORA_AUX_DISK_1: copied control file copy
    Finished restore at 30-AUG-12
    contents of Memory Script:
    sql clone 'alter database mount standby database';
    executing Memory Script
    sql statement: alter database mount standby database
    contents of Memory Script:
    set newname for tempfile 1 to
    "/u01/app/oradata/his/temp.266.750421813";
    set newname for tempfile 2 to
    "/u01/app/oradata/his/ts_temp_patrol.298.750425277";
    set newname for tempfile 3 to
    "/u01/app/oradata/his/ts_his_temp.296.750427905";
    set newname for tempfile 4 to
    "/u01/app/oradata/his/ts_tjjk_temp.282.750427917";
    set newname for tempfile 5 to
    "/u01/app/oradata/his/ts_temp_shuhao.595.782919539";
    switch clone tempfile all;
    set newname for datafile 1 to
    "/u01/app/oradata/his/system.256.750421615";
    set newname for datafile 2 to
    "/u01/app/oradata/his/sysaux.257.750421615";
    set newname for datafile 3 to
    "/u01/app/oradata/his/undotbs1.258.750421615";
    set newname for datafile 4 to
    "/u01/app/oradata/his/users.259.750421615";
    set newname for datafile 5 to
    "/u01/app/oradata/his/ts_his.280.750425023";
    set newname for datafile 6 to
    "/u01/app/oradata/his/ts_his_index.281.750425025";
    set newname for datafile 7 to
    "/u01/app/oradata/his/system.569.754307341";
    set newname for datafile 8 to
    "/u01/app/oradata/his/ts_bj.283.750425027";
    set newname for datafile 9 to
    "/u01/app/oradata/his/ts_gt.284.750425027";
    set newname for datafile 10 to
    "/u01/app/oradata/his/ts_fx.285.750425027";
    set newname for datafile 11 to
    "/u01/app/oradata/his/ts_uap.286.750425029";
    set newname for datafile 12 to
    "/u01/app/oradata/his/ts_gkxj.287.750425029";
    set newname for datafile 13 to
    "/u01/app/oradata/his/ts_xejj.288.750425031";
    set newname for datafile 14 to
    "/u01/app/oradata/his/ts_zdzyrz.289.750425031";
    set newname for datafile 15 to
    "/u01/app/oradata/his/ts_zj.290.750425033";
    set newname for datafile 16 to
    "/u01/app/oradata/his/ts_jgcp.291.750425033";
    set newname for datafile 17 to
    "/u01/app/oradata/his/ts_gtbj.292.750425033";
    set newname for datafile 18 to
    "/u01/app/oradata/his/ts_base.293.750425035";
    set newname for datafile 19 to
    "/u01/app/oradata/his/ts_exdata.294.750425035";
    set newname for datafile 20 to
    "/u01/app/oradata/his/ts_tjjk.295.750425037";
    set newname for datafile 21 to
    "/u01/app/oradata/his/ts_shuhao.594.782919537";
    set newname for datafile 22 to
    "/u01/app/oradata/his/ts_patrol.297.750425037";
    backup as copy reuse
    datafile 1 auxiliary format
    "/u01/app/oradata/his/system.256.750421615" datafile
    2 auxiliary format
    "/u01/app/oradata/his/sysaux.257.750421615" datafile
    3 auxiliary format
    "/u01/app/oradata/his/undotbs1.258.750421615" datafile
    4 auxiliary format
    "/u01/app/oradata/his/users.259.750421615" datafile
    5 auxiliary format
    "/u01/app/oradata/his/ts_his.280.750425023" datafile
    6 auxiliary format
    "/u01/app/oradata/his/ts_his_index.281.750425025" datafile
    7 auxiliary format
    "/u01/app/oradata/his/system.569.754307341" datafile
    8 auxiliary format
    "/u01/app/oradata/his/ts_bj.283.750425027" datafile
    9 auxiliary format
    "/u01/app/oradata/his/ts_gt.284.750425027" datafile
    10 auxiliary format
    "/u01/app/oradata/his/ts_fx.285.750425027" datafile
    11 auxiliary format
    "/u01/app/oradata/his/ts_uap.286.750425029" datafile
    12 auxiliary format
    "/u01/app/oradata/his/ts_gkxj.287.750425029" datafile
    13 auxiliary format
    "/u01/app/oradata/his/ts_xejj.288.750425031" datafile
    14 auxiliary format
    "/u01/app/oradata/his/ts_zdzyrz.289.750425031" datafile
    15 auxiliary format
    "/u01/app/oradata/his/ts_zj.290.750425033" datafile
    16 auxiliary format
    "/u01/app/oradata/his/ts_jgcp.291.750425033" datafile
    17 auxiliary format
    "/u01/app/oradata/his/ts_gtbj.292.750425033" datafile
    18 auxiliary format
    "/u01/app/oradata/his/ts_base.293.750425035" datafile
    19 auxiliary format
    "/u01/app/oradata/his/ts_exdata.294.750425035" datafile
    20 auxiliary format
    "/u01/app/oradata/his/ts_tjjk.295.750425037" datafile
    21 auxiliary format
    "/u01/app/oradata/his/ts_shuhao.594.782919537" datafile
    22 auxiliary format
    "/u01/app/oradata/his/ts_patrol.297.750425037" ;
    sql 'alter system archive log current';
    executing Memory Script
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    renamed tempfile 1 to /u01/app/oradata/his/temp.266.750421813 in control file
    renamed tempfile 2 to /u01/app/oradata/his/ts_temp_patrol.298.750425277 in control file
    renamed tempfile 3 to /u01/app/oradata/his/ts_his_temp.296.750427905 in control file
    renamed tempfile 4 to /u01/app/oradata/his/ts_tjjk_temp.282.750427917 in control file
    renamed tempfile 5 to /u01/app/oradata/his/ts_temp_shuhao.595.782919539 in control file
    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 backup at 30-AUG-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00008 name=+DATA/his/datafile/ts_bj.283.750425027
    channel ORA_DISK_2: starting datafile copy
    input datafile file number=00009 name=+DATA/his/datafile/ts_gt.284.750425027
    channel ORA_DISK_3: starting datafile copy
    input datafile file number=00005 name=+DATA/his/datafile/ts_his.280.750425023
    channel ORA_DISK_4: starting datafile copy
    input datafile file number=00015 name=+DATA/his/datafile/ts_zj.290.750425033
    RMAN-03009: failure of backup command on ORA_DISK_3 channel at 08/30/2012 16:10:23
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    channel ORA_DISK_3 disabled, job failed on it will be run on another channel
    RMAN-03009: failure of backup command on ORA_DISK_4 channel at 08/30/2012 16:42:19
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    channel ORA_DISK_4 disabled, job failed on it will be run on another channel
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 08/30/2012 16:51:58
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    channel ORA_DISK_2 disabled, job failed on it will be run on another channel
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/30/2012 17:49:09
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    channel ORA_DISK_1 disabled, job failed on it will be run on another channel
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 08/30/2012 17:49:09
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_4 channel at 08/30/2012 16:42:19
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 08/30/2012 16:51:58
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/30/2012 17:49:09
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    RMAN-03009: failure of backup command on ORA_DISK_3 channel at 08/30/2012 16:10:23
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    RMAN>
    Primary database alert log:
    Thu Aug 30 15:41:00 2012
    Clearing standby activation ID 3277937203 (0xc3615a33)
    The primary database controlfile was created using the
    'MAXLOGFILES 16' clause.
    There is space for up to 11 standby redo logfiles
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 536870912;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 536870912;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 536870912;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 536870912;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 536870912;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl6.f' SIZE 536870912;
    WARNING: OMF is enabled on this database. Creating a physical
    standby controlfile, when OMF is enabled on the primary
    database, requires manual RMAN intervention to resolve OMF
    datafile pathnames.
    NOTE: Please refer to the RMAN documentation for procedures
    describing how to manually resolve OMF datafile pathnames.
    Thu Aug 30 16:10:13 2012
    Errors in file /u01/oracle/diag/rdbms/his_primary/his/trace/his_ora_25860.trc (incident=72361):
    ORA-00600: internal error code, arguments: [1868], [0xFFFFFFFF7BBD4988], [], [], [], [], [], [], [], [], [], []
    Incident details in: /u01/oracle/diag/rdbms/his_primary/his/incident/incdir_72361/his_ora_25860_i72361.trc
    Thu Aug 30 16:10:20 2012
    Trace dumping is performing id=[cdmp_20120830161020]
    Thu Aug 30 16:10:22 2012
    Sweep [inc][72361]: completed
    Sweep [inc2][72361]: completed
    Thu Aug 30 16:40:32 2012
    Thread 1 cannot allocate new log, sequence 3031
    Private strand flush not complete
    Current log# 4 seq# 3030 mem# 0: +DATA/his_primary/onlinelog/group_4.579.759345057
    Current log# 4 seq# 3030 mem# 1: /backup/odsdb/HIS_PRIMARY/onlinelog/o1_mf_4_74nf15rq_.log
    Thread 1 advanced to log sequence 3031 (LGWR switch)
    Current log# 5 seq# 3031 mem# 0: +DATA/his_primary/onlinelog/group_5.261.759345075
    Current log# 5 seq# 3031 mem# 1: /backup/odsdb/HIS_PRIMARY/onlinelog/o1_mf_5_74nf1q2g_.log
    Thu Aug 30 16:40:37 2012
    LNS: Standby redo logfile selected for thread 1 sequence 3031 for destination LOG_ARCHIVE_DEST_2
    Thu Aug 30 16:40:39 2012
    Archived Log entry 5829 added for thread 1 sequence 3030 ID 0xffffffffc3615a33 dest 1:
    Thu Aug 30 16:42:15 2012
    Errors in file /u01/oracle/diag/rdbms/his_primary/his/trace/his_ora_25862.trc (incident=72369):
    ORA-00600: internal error code, arguments: [1868], [0xFFFFFFFF7BBD4988], [], [], [], [], [], [], [], [], [], []
    Incident details in: /u01/oracle/diag/rdbms/his_primary/his/incident/incdir_72369/his_ora_25862_i72369.trc
    Thu Aug 30 16:42:17 2012
    Trace dumping is performing id=[cdmp_20120830164217]
    Thu Aug 30 16:42:17 2012
    Sweep [inc][72369]: completed
    Sweep [inc2][72369]: completed
    Thu Aug 30 16:51:53 2012
    Errors in file /u01/oracle/diag/rdbms/his_primary/his/trace/his_ora_25858.trc (incident=72353):
    ORA-00600: internal error code, arguments: [1868], [0xFFFFFFFF7BBD4988], [], [], [], [], [], [], [], [], [], []
    Incident details in: /u01/oracle/diag/rdbms/his_primary/his/incident/incdir_72353/his_ora_25858_i72353.trc
    Thu Aug 30 16:51:55 2012
    Sweep [inc][72353]: completed
    Sweep [inc2][72353]: completed
    Thu Aug 30 16:51:55 2012
    Trace dumping is performing id=[cdmp_20120830165155]
    Edited by: 960892 on 2012-9-24 上午2:22

    hi:
    this is the initialization parameter file for auxiliary instance:
    *.audit_file_dest='/u01/oracle/admin/his/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='/u01/app/oradata/his/control01.ctl','/u01/app/oradata/his/control02.ctl','/u01/app/oradata/his/control03.ctl'
    *.db_block_size=8192
    *.db_domain='abc.com.cn'
    *.db_file_name_convert='+DATA/his/datafile/','/u01/app/oradata/his/','+DATA/his/tempfile/','/u01/app/oradata/his/','+DATA/his_primary/datafile/','/u01/app/oradata/his/','+DATA/his_primary/tempfile/','/u01/app/oradata/his/'
    *.db_files=1000
    *.db_name='his'
    *.db_recovery_file_dest='/backup/oracle'
    *.db_recovery_file_dest_size=1073741824000
    *.db_unique_name='his_standby_tt'
    *.diagnostic_dest='/u01/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=hisXDB)'
    *.fal_client='his_standby_tt'
    *.fal_server='his_primary'
    *.log_archive_config='DG_CONFIG=(his_primary,his_standby_tt)'
    *.log_archive_dest_1='LOCATION=/backup/oracle/HIS_STANDBY_TT/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=his_standby_tt'
    *.log_archive_dest_2='SERVICE=his_primary LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=his_primary'
    *.log_archive_dest_state_1='enable'
    *.log_archive_dest_state_2='enable'
    *.log_file_name_convert='+DATA/his_primary/onlinelog/','/u01/app/oradata/his/','/backup/odsdb/HIS_PRIMARY/onlinelog/','/u01/app/oradata/his/'
    *.memory_target=2181038080
    *.nls_language='SIMPLIFIED CHINESE'
    *.nls_territory='CHINA'
    *.open_cursors=300
    *.processes=3000
    *.remote_login_passwordfile='EXCLUSIVE'
    *.service_names='his.abc.com.cn,his_standby_tt.abc.com.cn'
    *.sessions=3305
    *.standby_file_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.event='10298 trace name context forever, level 32'

  • RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP

    First question.
    Can primary and standby database have the same SID name?
    As I recall it is yes.
    I believe they must have different GLOBAL or DB_UNIQUE_NAME?
    Anyway, RMAN I believe is telling me it is having problems copying control file on first and dies.
    Permissions Issue on STANDBY machine?
    RMAN> connect target backup_admin/backup_admin
    connected to target database: LABDG (DBID=1973403623)
    RMAN> connect auxiliary sys/oracle@STANDBY;
    connected to auxiliary database: LABDG (not mounted)
    RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE;
    Starting Duplicate Db at 18-JUL-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=10 device type=DISK
    contents of Memory Script:
    backup as copy reuse
    targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' auxiliar
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' ;
    executing Memory Script
    Starting backup at 18-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=151 device type=DISK
    Finished backup at 18-JUL-11
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format '/u01/oradat
    restore clone controlfile to '/u01/app/oracle/flash_recovery_area/LABDG/cont
    '/u01/oradata/LABDG/control01.ctl';
    executing Memory Script
    Starting backup at 18-JUL-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    copying standby control file
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/18/2011 11:20:54
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2011 11:20:
    ORA-17628: Oracle error 19505 returned by remote Oracle server

    Hi,
    Permissions Issue on STANDBY machine?First problem I see is the sysdba password must be the same on both sides (target and auxiliary dbs).
    From the documentation.
    The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can
    create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.Check all prereqs for the standby db duplicate here.
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
    Rgds,
    Tycho

  • RMAN DUPLICATE FOR STANDBY FROM ACTIVE DATABASE fails

    Hello
    I'm trying to use RMAN DUPLICATE to create a standby database using Oracle 11.2.0.3 with PSU 6 on HP-UX.
    Primary is 2 node RAC. Standby is also 2 node RAC.
    Standby database instance is started in nomount mode.
    I use:
    duplicate target database for standby from active database
      spfile
      <some spfile parameters>
    with PFILE I get:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/01/2013 12:41:13
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of sql command on clone_default channel at 10/01/2013 12:41:13
    RMAN-11003: failure during parse/execution of SQL statement: alter system set spfile= '/opt/oracle/db11203/dbs/spfileCU1.ora'
    ORA-02097: parameter cannot be modified because specified value is invalid
    ORA-01565: error in identifying file '/opt/oracle/db11203/dbs/spfileCU1.ora'
    ORA-27037: unable to obtain file status
    HPUX-ia64 Error: 2: No such file or directory
    With SPFILE I get;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/01/2013 13:06:34
    RMAN-05501: aborting duplication of target database
    RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause
    But I do have RMAN connexion to target database.
    Thanks for your help.

    Here is the output beginning of the script which clearly shows that I'm always connected to target database:
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 1 13:05:47 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CU (DBID=1143962925)
    connected to auxiliary database: CU (not mounted)
    RMAN> set echo on
    2> run
    3> {
    4>  configure device type disk parallelism 10;
    5>   allocate channel pr1 type disk;
    6>   allocate channel pr2 type disk;
    7>   allocate channel pr3 type disk;
    8>   allocate channel pr4 type disk;
    9>   allocate channel pr5 type disk;
    10>   allocate channel pr6 type disk;
    11>   allocate channel pr7 type disk;
    12>   allocate channel pr8 type disk;
    13>   allocate channel pr9 type disk;
    14>   allocate channel pr10 type disk;
    15>   allocate auxiliary channel st1 type disk;
    16>   allocate auxiliary channel st2 type disk;
    17>   allocate auxiliary channel st3 type disk;
    18>   allocate auxiliary channel st4 type disk;
    19>   allocate auxiliary channel st5 type disk;
    20>   allocate auxiliary channel st6 type disk;
    21>   allocate auxiliary channel st7 type disk;
    22>   allocate auxiliary channel st8 type disk;
    23>   allocate auxiliary channel st9 type disk;
    24>   allocate auxiliary channel st10 type disk;
    25>   duplicate target database for standby from active database
    26>   spfile

  • Why do we use RMAN DUPLICATE for cloning DB on a different server ?

    DB version : 11.2.0.2, 10.2.0.5
    I want to create a clone of my Production DB in a test server. In the past, I have taken hot backup of this production DB and restored and recovered it in a different server using plain RMAN commands.
    After restoring the control file , mounting the DB and cataloging the backup pieces in the test server , I run
    run {
    restore database ;
    recover database until time <time> ;
    alter database open resetlogs ;
    }In OTN , i came across long running discussions like
    RMAN duplicate database
    where they are trying to restore and recover using DUPLICATE command as shown below.
    run
    duplicate target database to RBS
    nofilenamecheck
    pfile=/tmp/aux.ora;
    Can't they just use plain RMAN restore and recover commands as I did ? What advantage does RMAN DUPLICATE have over the plain commands ?

    RMAN DUPLICATE is designed to give to clone database a new database name and new database identifier:
    >
    If you copy a database with operating system utilities instead of the DUPLICATE command, then the DBID of the copied database remains the same as the original database. To register the copy database in the same recovery catalog with the original, you must change the DBID with the DBNEWID utility (see Oracle Database Utilities). In contrast, the DUPLICATE command automatically assigns the duplicate database a different DBID so that it can be registered in the same recovery catalog as the source database.

  • How duplicate ora11 on windows to another host with different directory structure

    Hi,
    I need help.
    I want to duplicate db (11.2) running on windows from server A to Server B
    Directory structures on server A and Server B are different;
    my steps
    on server A
    1.backup database plus archivelog delete input;
    2.insert into table t values(1);
    3.commit;
    4.backup archive log all;
    On Server B
    5.copy backup and archive logs from server A to server B (c:\backup\temp)
    6.create folders C:\oracle\oradata\bamboo
    7.oradim –new –sid bamboo -- (verified service is running)
    8. created pfile.ora with param (db_name=bamboo)
    9.SET oracle_SID=bamboo
    10.sqlplus  /as sysdba
    11.startup nomount pfile='(c:\backup\temp\pfile.ora'
    12.C:\oracle\product\11.2.0\db_1\database>rman auxiliary /
    result
    ..connected to auxiliary database: SBDBT02W (DBID=186082786, not open)  --could it be the fact that I tried to execute code bellow?
    My understanding at this point I should be connected to 'bamboo' -- my new database, what steps did I miss?
    I expect
    ..connected to auxiliary database: bamboo ( not mounted)
    bellow is code that I was going to run on Server B
    RUN
      SET NEWNAME FOR DATAFILE 1 TO 'C:\oracle\oradata\bamboo\SYSTEM01.DBF';
      SET NEWNAME FOR DATAFILE 2 TO 'C:\oracle\oradata\bamboo\SYSAUX01.DBF';
      SET NEWNAME FOR DATAFILE 3 TO 'C:\oracle\oradata\bamboo\UNDOTBS01.DBF';
      SET NEWNAME FOR DATAFILE 4 TO 'C:\oracle\oradata\bamboo\USERS01.DBF';
      SET NEWNAME FOR DATAFILE 5 TO 'C:\oracle\oradata\bamboo\EXAMPLE01.DBF';
      DUPLICATE DATABASE TO bamboo
      UNTIL TIME "TO_DATE('11/24/2013 13:18:02', 'MM/DD/YYYY HH24:MI:SS')"
      BACKUP LOCATION 'C:\backup\temp'
      NOFILENAMECHECK;
    when I executed it on Server B ,I got following error
    Starting Duplicate Db at 25-NOV-13
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 11/25/2013 11:27:36
    RMAN-05500: the auxiliary database must be not mounted when issuing a DUPLICATE
    command
    I looking for steps by step instruction for duplicating db to another windows host with different directory structure.
    Thank you
    Alex

    The topic, "Duplicating a Database on a Remote Host with a Different Directory Structure" can be found at http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1006672
    This information should provide you the step by step process to follow including when on Windows.
    HTH -- Mark D Powell --

  • Oracle 10.2.0.4 RMAN Duplicate without a Recovery Catalog

    Production Backups are Tuesday - Sunday at 22:00:
    RUN {
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    CROSSCHECK ARCHIVELOG ALL;
    CROSSCHECK BACKUP;
    DELETE NOPROMPT COPY OF ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';
    DELETE NOPROMPT BACKUP;
    BACKUP DATABASE PLUS ARCHIVELOG;
    CROSSCHECK BACKUP;
    RELEASE CHANNEL c1;
    LIST BACKUPSET;
    EOF
    I have these files sent over to the development server on Wednesday, RMANbackup (log), backupset and the controlfile:
    rcp -rp /backup/$1/flash_recovery/$2/RMANbackup/* kacdb4:/backup/common/flash_recovery/$2/RMANbackup
    rcp -rp /backup/$1/flash_recovery/$2/backupset/* kacdb4:/backup/common/flash_recovery/$2/backupset
    rcp -rp /backup/$1/flash_recovery/$2/controlfile/* kacdb4:/backup/common/flash_recovery/$2/controlfile
    I run the RMAN Duplicate and the database gets created with no problems!
    The question is: If I wait unit Thursday, to run the duplicate script, I get the traditional RMAN errors: RMAN-03002, RMAN-03015, RMAN-06026, RMAN-06023:
    Starting restore at 20-SEP-12
    released channel: aux1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/20/2012 10:05:36
    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 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
    Recovery Manager complete.
    Is this because of the 'SYSDATE-2' in the RMAN runlist? Does RMAN connect back to the target and it does not find the logs, because they've been deleted, it aborts the duplicate? I've shipped over the backupset and controlfile of the scn I'm using in the duplicate runlist all is there? If I'm trying to cleanup the archive area, would'nt 'delete expired archivelog all' in my runlist, be better than using the 'SYSDATE-2'?
    Or is it because of this database parameter:
    control_file_record_keep_time= 7, should I set this to say 14?
    Is it one of these RMAN configurations:
    Retention Policy to Redundancy 1, should I set this to say 7?
    Datafile Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space which is precious
    Archivelog Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space too
    Archive deletion policy to none change this to the other option?
    I've tested this a few times now, and always fails if the dupicate is not done the next day.
    If I have to create a development database on a Friday from Tuesday's copy FROM TAPE, I will get the error, because the files are no longer on disk.
    What can I do to ensure that I can create an RMAN duplicate any day of the week from Tuesday to Sunday?
    Look forward to your answer.
    Please let me know if I left any details out that you may need.
    Sincerely,
    Elizabeth Burns

    Hi Valentin,
    Here is the good duplicate log from Monday 9/24:
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120924.log
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:32 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
    SQL> shutdown immediate
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> spool off
    SQL> exit;
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:41 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected to an idle instance.
    File created.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:43 2012
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: KEDSP (DBID=3370721566)
    connected to auxiliary database: DUPDB (not mounted)
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4>
    5> set until scn 211054288;
    6> DUPLICATE TARGET DATABASE TO dupdb
    7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
    8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
    r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
    /','/usr/
    9> local/OLlinks/dupdb/index01/')
    10> LOGFILE
    11> GROUP 1 (
    12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
    13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
    14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
    15> ) SIZE 50M,
    16> GROUP 2 (
    17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
    18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
    19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
    20> ) SIZE 50M,
    21> GROUP 3 (
    22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
    23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
    24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
    25> ) SIZE 50M,
    26> GROUP 4 (
    27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
    28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
    29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
    30> ) SIZE 50M,
    31> GROUP 5 (
    32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
    33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
    34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
    35> ) SIZE 50M,
    36> GROUP 6 (
    37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
    38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
    39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
    40> ) SIZE 50M,
    41> GROUP 7 (
    42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
    43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
    44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
    45> ) SIZE 50M,
    46> GROUP 8 (
    47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
    48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
    49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
    50> ) SIZE 50M,
    51> GROUP 9 (
    52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
    53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
    54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
    55> ) SIZE 50M,
    56> GROUP 10 (
    57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
    58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
    59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
    60> ) SIZE 50M
    61> ;
    62> }
    63>
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=242 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 24-SEP-12
    contents of Memory Script:
    set until scn 211054288;
    set newname for datafile 1 to
    "/usr/local/OLlinks/dupdb/system/system01.dbf";
    set newname for datafile 2 to
    "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    set newname for datafile 3 to
    "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    set newname for datafile 4 to
    "/usr/local/OLlinks/dupdb/system/users01.dbf";
    set newname for datafile 5 to
    "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    set newname for datafile 6 to
    "/usr/local/OLlinks/dupdb/index01/index1.dbf";
    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
    executing command: SET NEWNAME
    Starting restore at 24-SEP-12
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /usr/local/OLlinks/dupdb/system/system01.dbf
    restoring datafile 00002 to /usr/local/OLlinks/dupdb/system/undotbs01.dbf
    restoring datafile 00003 to /usr/local/OLlinks/dupdb/system/sysaux01.dbf
    restoring datafile 00004 to /usr/local/OLlinks/dupdb/system/users01.dbf
    restoring datafile 00005 to /usr/local/OLlinks/dupdb/data01/data1.dbf
    restoring datafile 00006 to /usr/local/OLlinks/dupdb/index01/index1.dbf
    channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T1
    01837_860txxs8_.bkp
    channel aux1: restored backup piece 1
    piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T101837_860txxs8_.bkp tag=TAG
    20120924T101837
    channel aux1: restore complete, elapsed time: 00:00:47
    Finished restore at 24-SEP-12
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 584
    LOGFILE
    GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
    db/redo03/redo0103.log' ) SIZE 50 M ,
    GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
    db/redo03/redo0203.log' ) SIZE 50 M ,
    GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
    db/redo03/redo0303.log' ) SIZE 50 M ,
    GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
    db/redo03/redo0403.log' ) SIZE 50 M ,
    GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
    db/redo03/redo0503.log' ) SIZE 50 M ,
    GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
    db/redo03/redo0603.log' ) SIZE 50 M ,
    GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
    db/redo03/redo0703.log' ) SIZE 50 M ,
    GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
    db/redo03/redo0803.log' ) SIZE 50 M ,
    GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
    db/redo03/redo0903.log' ) SIZE 50 M ,
    GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
    db/redo03/redo1003.log' ) SIZE 50 M
    DATAFILE
    '/usr/local/OLlinks/dupdb/system/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=794858918 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=794858918 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
    contents of Memory Script:
    set until scn 211054288;
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 24-SEP-12
    starting media recovery
    channel aux1: starting archive log restore to default destination
    channel aux1: restoring archive log
    archive log thread=1 sequence=1403
    channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T1
    01923_860tzfd7_.bkp
    channel aux1: restored backup piece 1
    piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T101923_860tzfd7_.bkp tag=TAG
    20120924T101923
    channel aux1: restore complete, elapsed time: 00:00:05
    archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc thread=1 sequenc
    e=1403
    channel clone_default: deleting archive log(s)
    archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc recid=1 stamp=79
    4858923
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 24-SEP-12
    contents of Memory Script:
    shutdown clone;
    startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora';
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 584
    LOGFILE
    GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
    db/redo03/redo0103.log' ) SIZE 50 M ,
    GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
    db/redo03/redo0203.log' ) SIZE 50 M ,
    GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
    db/redo03/redo0303.log' ) SIZE 50 M ,
    GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
    db/redo03/redo0403.log' ) SIZE 50 M ,
    GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
    db/redo03/redo0503.log' ) SIZE 50 M ,
    GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
    db/redo03/redo0603.log' ) SIZE 50 M ,
    GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
    db/redo03/redo0703.log' ) SIZE 50 M ,
    GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
    db/redo03/redo0803.log' ) SIZE 50 M ,
    GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
    db/redo03/redo0903.log' ) SIZE 50 M ,
    GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
    db/redo03/redo1003.log' ) SIZE 50 M
    DATAFILE
    '/usr/local/OLlinks/dupdb/system/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
    set newname for tempfile 1 to
    "/usr/local/OLlinks/dupdb/temp/temp01.dbf";
    switch clone tempfile all;
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/users01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/index01/index1.dbf";
    switch clone datafile all;
    executing Memory Script
    executing command: SET NEWNAME
    renamed temporary file 1 to /usr/local/OLlinks/dupdb/temp/temp01.dbf in control file
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf recid=1 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf recid=2 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/users01.dbf recid=3 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/data01/data1.dbf recid=4 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/index01/index1.dbf recid=5 stamp=794858932
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=794858932 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=794858932 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    database opened
    Finished Duplicate Db at 24-SEP-12
    Recovery Manager complete.
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:09:39 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    User altered.
    User altered.
    User altered.
    User altered.
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Database mounted.
    Database altered.
    Database altered.
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
    Here is the duplicate log from this morning:
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120926.log
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:31 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> spool off
    SQL> exit;
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:42 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected to an idle instance.
    File created.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    Recovery Manager: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:45 2012
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: KEDSP (DBID=3370721566)
    connected to auxiliary database: DUPDB (not mounted)
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4>
    5> set until scn 211054288;
    6> DUPLICATE TARGET DATABASE TO dupdb
    7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
    8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
    r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
    /','/usr/
    9> local/OLlinks/dupdb/index01/')
    10> LOGFILE
    11> GROUP 1 (
    12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
    13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
    14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
    15> ) SIZE 50M,
    16> GROUP 2 (
    17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
    18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
    19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
    20> ) SIZE 50M,
    21> GROUP 3 (
    22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
    23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
    24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
    25> ) SIZE 50M,
    26> GROUP 4 (
    27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
    28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
    29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
    30> ) SIZE 50M,
    31> GROUP 5 (
    32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
    33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
    34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
    35> ) SIZE 50M,
    36> GROUP 6 (
    37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
    38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
    39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
    40> ) SIZE 50M,
    41> GROUP 7 (
    42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
    43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
    44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
    45> ) SIZE 50M,
    46> GROUP 8 (
    47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
    48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
    49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
    50> ) SIZE 50M,
    51> GROUP 9 (
    52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
    53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
    54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
    55> ) SIZE 50M,
    56> GROUP 10 (
    57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
    58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
    59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
    60> ) SIZE 50M
    61> ;
    62> }
    63>
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=242 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 26-SEP-12
    contents of Memory Script:
    set until scn 211054288;
    set newname for datafile 1 to
    "/usr/local/OLlinks/dupdb/system/system01.dbf";
    set newname for datafile 2 to
    "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    set newname for datafile 3 to
    "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    set newname for datafile 4 to
    "/usr/local/OLlinks/dupdb/system/users01.dbf";
    set newname for datafile 5 to
    "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    set newname for datafile 6 to
    "/usr/local/OLlinks/dupdb/index01/index1.dbf";
    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
    executing command: SET NEWNAME
    Starting restore at 26-SEP-12
    released channel: aux1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/26/2012 08:28:53
    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 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
    Recovery Manager complete.
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:53 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    alter user sys identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user system identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user dbsnmp identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user sysman identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    ORA-01507: database not mounted
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    ORA-00205: error in identifying control file, check alert log for more info
    alter database noarchivelog
    ERROR at line 1:
    ORA-01507: database not mounted
    alter database open
    ERROR at line 1:
    ORA-01507: database not mounted
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
    Please let me know if you need anything else.
    Sincerely,
    Elizabeth

  • Oracle EE 11.2.0.2 RMAN Duplicate interesting issue - is it a bug?

    Hi,
    Oracle EE 11.2.0.2 RHEL 5.7 x86 64-bit RACOne Node database (3 - nodes).
    I was working on a process to refresh out test environment with prod database backup from tape and i have done it many times. Most of our environment is in 10gR2 and have few on 11.2.0.2 RACOne Node databases. The recovery basics in Oracle world is to use archive log sequence + 1 (provided we know before hand the backups metadata) and it works as expected until 10g but with 11.2.0.2 RMAN duplicate, i stumbled upon an issue where RMAN is trying to restore an older controlfile auto backup and then rolling forward from there. Its easy to explain with an example..
    1) I have an archivelog backup, say sequence 20 to 30 on Feb 22nd @ 10pm and a controlfile autobackup at this time c-20120222
    2) I have a FULL backup + archive log until sequence 50 on Feb 23nd@ 6pm and a controlfile autobackup at this time  c-20120223
    3) I am using RMAN duplicate to refresh UAT with Feb 23rd backup and use "set until sequence 51 thread 1"I am using following RMAN commands to do the duplicate on UAT server (executed on UAT server)
    rman target sys/***@PROD_DB  auxiliary /
    RMAN> run
    2> {
    3> allocate auxiliary channel c1 device type disk;
    4> allocate auxiliary channel c2 device type disk;
    5> allocate auxiliary channel c3 device type disk;
    6> set until sequence 51 thread 1;
    7> duplicate target database to UAT_DB;
    8> }RMAN duplicate automates all that we do manually but the recovery mechanism is same. In the above scenario, it connects to target database, gets the backup metadata and restores controlfile from c-20120223 , restores the datafiles and recovers till sequence 50 . This has been the scenario until 10g in every RMAN duplicate process i have tried and is expected from Oracle.
    Issue:
    In 11gR2 (11.2.0.2), for the same duplicate scenario above, it is restoring the controlfile from autobackup c-20120222 and restoring the datafiles from Feb 23rd backup, recovering till sequence 50 and doing the duplicate process. The thing to note here is that the controlfile autobackup c-20120222 does not have any record of the FULL backup that occured on Feb 23 rd and since RMAN duplicate is having a connection to target database, it knows the backup metadata and hence it is able to complete the recovery.
    For clarification, Thread 1 & 2 of RAC One Node is not an issue here for sure. Did anyone experience this issue? Any insight into this would be greatly appreciated.
    Thanks,
    Shiva

    AJ,
    I have already tried that scenario, i renamed the c-20120222 and kicked off the same duplicate process but it failed and it kept on "fail-over to previous backup" which is expected. The thing is, RMAN look's for the control file autobackups from newest to oldest (unless you gave a point in time) and duplicate command is not doing it.
    Tycho,
    I agree there are new features but to support them a change in recovery mechanism is something i would disagree that Oracle would do. Active Duplication is not based on backups, so that is out of question here. For backup-based duplication, we can try with connections to target or targetless, catalog or catalogless or none. I have already given an example with the target (same with target + catalog) and i expect the same behavior with only catalog connection. Now, i have tested the example without connecting to target or catalog and below are my observations...
    For the same backups i mentioned in the very first email, i got the following info....
    rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Fri Feb 24 12:35:54 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: RMANTEST (DBID=3789692530)
    RMAN> list backup of archivelog sequence 95;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    11      2.50K      DISK        00:00:00     23-FEB-12 18:05:40
            BP Key: 11   Status: AVAILABLE  Compressed: YES  Tag: TAG20120222T094240
            Piece Name: /u01/app/oracle/exp/rmantest_stl/full_backup/rmantest_stl_0bn3upkg_1_1.arch
      List of Archived Logs in backup set 11
      Thrd Seq     Low SCN    Low Time           Next SCN   Next Time
      1    95      346280     23-FEB-12 18:05:10 346302     23-FEB-12 18:05:30I got the scn_to_timestamp for the NEXT_SCN of sequence 95, which should correpond tothe "Next Time" that is the timestamp for the Archive log sequence 96.
    SQL> select scn_to_timestamp(346302) as timestamp from dual;
    TIMESTAMP
    23-FEB-12 18.05.30.000000000 PMNow, i gave the following for targetless & catalogless duplication...
    rman auxiliary /
    RMAN> run
    2> {
    3> set until time "to_date('23-FEB-12 18:05:30','DD-MON-YY HH24:MI:SS')";
    4> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
    5> }RESULT: Same ISSUE but this time IT FAILED with the error i expected. It went ahead and restored the c-20120222 autobackup control file and tried to restore the datafiles but, as we
    know, this control file autobackup does not have record of Feb 23rd + archive log backup, so it FAILS. This is exactly what i told in my first email.
    Error Log File:
    contents of Memory Script:
       sql clone "alter system set  control_files =
      ''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776081841'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776081841'' comment=
    ''Set by RMAN'' scope=spfile";
       sql clone "alter system set  db_name =
    ''RMANTEST'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile from  '/u01/app/oracle/exp/rmantest_stl/c-20120222';
       alter clone database mount;
    Errors in memory script
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01507: database not mounted
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 13371
    ORA-06512: at line 1
    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 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-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/24/2012 10:18:04
    RMAN-05501: aborting duplication of target databaseSo, my next test was not to give any Point In Time, that is just issue the duplicate without SET UNIL clause and this time, and this time it behaved, it restored the control file from c-20120223 and completed the duplicate process. So what does this tell us? We cannot do a POINT IN TIME duplicate using RMAN DUPLICATE????
    rman auxiliary /
    RMAN> run
    2> {
    3> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
    4> }
    contents of Memory Script:
       sql clone "alter system set  control_files =
      ''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776089489'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776089489'' comment=
    ''Set by RMAN'' scope=spfile";
       sql clone "alter system set  db_name =
    ''RMANTEST'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile from  '/u01/app/oracle/exp/rmantest_stl/c-20120223';
       alter clone database mount;
    }Just checking if anyone stumbled upon these findings. An Oracle SR is already in place, so just waiting for an update from them.
    Thanks,
    Shiva

  • "Segmentation fault" during tns rman active duplicate

    Hello. I am trying to do an active duplicate using tns connectivity and just after restoring the controlfile the process fails with the error "Segmentation fault". However if I start the rman using Ezconnect everything goes smoothly. Restarting the databases did not help. What could be the reason? Here is the output with the error:
    rman target sys/oracle@EN9 auxiliary sys/oracle@EN910
    Recovery Manager: Release 11.2.0.3.0 - Production on Thu Jun 13 17:41:15 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: EN9 (DBID=529480944)
    connected to auxiliary database: EN910 (not mounted)
    RMAN> duplicate target database to EN910 from active database nofilenamecheck;
    Starting Duplicate Db at 13-JUN-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=24 device type=DISK
    contents of Memory Script:
       sql clone "alter system set  control_files =
      ''+DATA/en910/controlfile/current.271.818012497'' comment=
    ''Set by RMAN'' scope=spfile";
       sql clone "alter system set  db_name =
    ''EN9'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       sql clone "alter system set  db_unique_name =
    ''EN910'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       backup as copy current controlfile auxiliary format  '+DATA/en910/controlfile/current.275.818012497';
       sql clone "alter system set  control_files =
      ''+DATA/en910/controlfile/current.275.818012497'' comment=
    ''Set by RMAN'' scope=spfile";
       shutdown clone immediate;
       startup clone nomount;
       alter clone database mount;
    executing Memory Script
    sql statement: alter system set  control_files =   ''+DATA/en910/controlfile/current.271.818012497'' comment= ''Set by RMAN'' scope=spfile
    sql statement: alter system set  db_name =  ''EN9'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set  db_unique_name =  ''EN910'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    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
    Starting backup at 13-JUN-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=25 device type=DISK
    channel ORA_DISK_1: starting datafile copy
    copying current control file
    Oracle instance started
    Segmentation fault
    tnsnames.ora of target db:
    EN9 =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ora9)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = EN9)
    tnsnames.ora of aux db:
    EN910 =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ora10)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = EN910)
    EN9 =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ora9)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = EN9)
    listener.ora of aux db:
    SID_LIST_LISTENER =
            (SID_LIST =
                    (SID_DESC =
                            (GLOBAL_DBNAME=EN910)
                            (ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)
                            (SID_NAME=EN910)

    if you have access to MOS:
    Rman Duplicate Fails With Segmentation Fault [ID 744717.1]
    Rman Duplicate Failing With A Segmentation Fault [ID 1092423.1]

  • Regarding duplicate database

    Dear Experts
    Pls give me solution for my problem..
    I am working on Oracle 10.2 running on rhel 4.I am trying to create duplicate database on the same host as on target.My target database is in archive log mode. When i am trying to fire the above command I get following error. Here are the steps..
    [oracle@infotech ~]$ rman target / auxiliary sys/admin@dupli
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Jan 27 12:50:25 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: SQLSTAR (DBID=1533334878, not open)
    connected to auxiliary database: DUPLI (not mounted)
    RMAN> duplicate target database to dupli
    2> logfile
    3> '/database/dupli/log/redo01.log' size 10m,
    4> '/database/dupli/log1/redo02.log' size 10m;
    Starting Duplicate Db at 27-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=153 devtype=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: sid=154 devtype=DISK
    allocated channel: ORA_AUX_DISK_3
    channel ORA_AUX_DISK_3: sid=156 devtype=DISK
    allocated channel: ORA_AUX_DISK_4
    channel ORA_AUX_DISK_4: sid=157 devtype=DISK
    datafile 5 not processed because file is offline
    datafile 6 not processed because file is offline
    contents of Memory Script:
    set until scn 2404769;
    set newname for datafile 1 to
    "/database/dupli/data/system01.dbf";
    set newname for datafile 2 to
    "/database/dupli/data/undotbs01.dbf";
    set newname for datafile 3 to
    "/database/dupli/data/sysaux01.dbf";
    set newname for datafile 4 to
    "/database/dupli/data/users01.dbf";
    restore
    check readonly
    clone database
    skip tablespace TRY,
    PROD ;
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 27-JAN-11
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    using channel ORA_AUX_DISK_3
    using channel ORA_AUX_DISK_4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/27/2011 12:55:35
    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 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
    Although I am having the backups
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    58 Full 6.86M DISK 00:00:01 27-JAN-11
    BP Key: 57 Status: AVAILABLE Compressed: NO Tag: TAG20110127T105501
    Piece Name: /database/sqlstar/flash/SQLSTAR/backupset/2011_01_27/o1_mf_ncnnf_TAG20110127T105501_6n20fh2b_.bkp
    Control File Included: Ckp SCN: 2428375 Ckp time: 27-JAN-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    59 Full 80.00K DISK 00:00:04 27-JAN-11
    BP Key: 58 Status: AVAILABLE Compressed: NO Tag: TAG20110127T105501
    Piece Name: /database/sqlstar/flash/SQLSTAR/backupset/2011_01_27/o1_mf_nnsnf_TAG20110127T105501_6n20fmbz_.bkp
    SPFILE Included: Modification time: 27-JAN-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    60 Full 370.27M DISK 00:01:41 27-JAN-11
    BP Key: 59 Status: AVAILABLE Compressed: NO Tag: TAG20110127T105501
    Piece Name: /database/sqlstar/flash/SQLSTAR/backupset/2011_01_27/o1_mf_nnndf_TAG20110127T105501_6n20fh6k_.bkp
    List of Datafiles in backup set 60
    File LV Type Ckp SCN Ckp Time Name
    2 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/undotbs01.dbf
    3 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/sysaux01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    61 Full 339.97M DISK 00:01:57 27-JAN-11
    BP Key: 60 Status: AVAILABLE Compressed: NO Tag: TAG20110127T105501
    Piece Name: /database/sqlstar/flash/SQLSTAR/backupset/2011_01_27/o1_mf_nnndf_TAG20110127T105501_6n20fkq2_.bkp
    List of Datafiles in backup set 61
    File LV Type Ckp SCN Ckp Time Name
    1 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/system01.dbf
    6 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/try01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    62 Full 652.93M DISK 00:02:15 27-JAN-11
    BP Key: 61 Status: AVAILABLE Compressed: NO Tag: TAG20110127T105501
    Piece Name: /database/sqlstar/flash/SQLSTAR/backupset/2011_01_27/o1_mf_nnndf_TAG20110127T105501_6n20fjkw_.bkp
    List of Datafiles in backup set 62
    File LV Type Ckp SCN Ckp Time Name
    4 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/users01.dbf
    5 Full 2428375 27-JAN-11 /database/sqlstar/data/sqlstar/prod01.db
    Regards
    Asif

    Dear Experts
    As per your suggestion I havle allocated multiple channels including the auxliary channel..*It has executed to a lot of extent but it has hung at last*.I am posting the commands and steps..
    [oracle@infotech ~]$ rman target / auxiliary sys/admin@dupli
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 28 11:46:07 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: SQLSTAR (DBID=1533334878)
    connected to auxiliary database: DUPLI (not mounted)
    RMAN> run{
    2> allocate channel c1 type disk;
    3> allocate channel c2 type disk;
    4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    5> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    6> duplicate target database to dupli;
    7> }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: sid=140 devtype=DISK
    allocated channel: c2
    channel c2: sid=139 devtype=DISK
    allocated channel: aux1
    channel aux1: sid=155 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=154 devtype=DISK
    Starting Duplicate Db at 28-JAN-11
    contents of Memory Script:
    set until scn 2487653;
    set newname for datafile 1 to
    "/u01/dupli/data/system01.dbf";
    set newname for datafile 2 to
    "/u01/dupli/data/undotbs01.dbf";
    set newname for datafile 3 to
    "/u01/dupli/data/sysaux01.dbf";
    set newname for datafile 4 to
    "/u01/dupli/data/users01.dbf";
    set newname for datafile 5 to
    "/u01/dupli/data/prod01.dbf";
    set newname for datafile 6 to
    "/u01/dupli/data/try01.dbf";
    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
    executing command: SET NEWNAME
    Starting restore at 28-JAN-11
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00002 to /u01/dupli/data/undotbs01.dbf
    restoring datafile 00003 to /u01/dupli/data/sysaux01.dbf
    channel aux1: reading from backup piece /u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qkhf6_.bkp
    channel aux2: starting datafile backupset restore
    channel aux2: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/dupli/data/system01.dbf
    restoring datafile 00006 to /u01/dupli/data/try01.dbf
    channel aux2: reading from backup piece /u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qkb92_.bkp
    channel aux1: restored backup piece 1
    piece handle=/u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qkhf6_.bkp tag=TAG20110128T114150
    channel aux1: restore complete, elapsed time: 00:01:16
    channel aux2: restored backup piece 1
    piece handle=/u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qkb92_.bkp tag=TAG20110128T114150
    channel aux2: restore complete, elapsed time: 00:01:17
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00004 to /u01/dupli/data/users01.dbf
    restoring datafile 00005 to /u01/dupli/data/prod01.dbf
    channel aux1: reading from backup piece /u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qk8lg_.bkp
    channel aux1: restored backup piece 1
    piece handle=/u01/flash/SQLSTAR/backupset/2011_01_28/o1_mf_nnndf_TAG20110128T114150_6n4qk8lg_.bkp tag=TAG20110128T114150
    channel aux1: restore complete, elapsed time: 00:01:15
    Finished restore at 28-JAN-11
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPLI" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 2 ( '/u01/dupli/log/redo02.log' ) SIZE 50 M REUSE,
    GROUP 3 ( '/u01/dupli/log/redo03.log' ) SIZE 50 M REUSE,
    GROUP 4 ( '/u01/dupli/log/redo05.log' ) SIZE 100 M REUSE
    DATAFILE
    '/u01/dupli/data/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=741613900 filename=/u01/dupli/data/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=741613900 filename=/u01/dupli/data/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=741613900 filename=/u01/dupli/data/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=741613900 filename=/u01/dupli/data/prod01.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=741613900 filename=/u01/dupli/data/try01.dbf
    contents of Memory Script:
    set until scn 2487653;
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 28-JAN-11
    starting media recovery
    archive log thread 1 sequence 142 is already on disk as file /u01/flash/SQLSTAR/archivelog/2011_01_28/o1_mf_1_142_6n4qqom4_.arc
    archive log filename=/u01/flash/SQLSTAR/archivelog/2011_01_28/o1_mf_1_142_6n4qqom4_.arc thread=1 sequence=142
    media recovery complete, elapsed time: 00:00:04
    Finished recover at 28-JAN-11
    contents of Memory Script:
    shutdown clone;
    startup clone nomount ;
    executing Memory Script

  • Duplicate by RMAN in 10g

    Hi,
    to duplicate a databse to an auxiliary DB, auxiliary should be in nomount.
    please See 374069.1 note on metalink or Oracle® Data Guard
    Concepts and Administration 10g Release 2 (10.2) B14239-04 page F-7.
    But,
    RMAN can not connect to an auxiliary oracle database when it is in nomount state. I created another
    data base named orcl3. Impossible to conect to by RMAN as auxiliary for orcl2
    and orcl3 :
    orcl2 is in noumount :
    C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
    connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
    RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
    I did :
    SQL>alter database mount
    and now :
    C:\Documents and Settings\ >rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
    Regards.
    Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:02:21 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target : ORCL (DBID=1155329895)
    connected to auxiliaire : ORCL2 (DBID=608821149, non ouverte)
    RMAN> exit
    orcl3 is nomounted :
    C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary
    sys/pwd@orcl3
    Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:31:55 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
    RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
    Many thanks.

    Hi Damorgan,
    you are true, RMAN connected :
    C:\Documents and Settings\user>rman target sys/pwd@orcl auxiliary /
    Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 15:37:46 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target : ORCL (DBID=1155329895)
    connected to auxiliary : ORCL2 (non mounted)
    But :
    When :
    RMAN> run{
    2> duplicate target database for standby
    3> nofilenamecheck
    4> dorecover;
    5> }
    canal ORA_AUX_DISK_1 : restauration de fichier de contr¶le
    canal ORA_AUX_DISK_1 : copie du fichier de contr¶le copiÚe
    fichier en entrÚe=C:\ORACLE\ORADATA\BACKUP\ORCL\CONTROL01.DBF
    fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL01.CTL
    fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL02.CTL
    fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL03.CTLFin de restore dans 04/08/07
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Failed in Duplicate DB 08/04/2007 15:43:10
    RMAN-03015: une erreur s'est produite dans le script stockÚ Memory Script
    RMAN-03009: Úchec de la commande sql sur le canal clone_default Ó 08/04/2007 15:43:10
    RMAN-11003: erreur lors de l'analyse ou de l'exÚcution d'une instruction SQL : alter database mount standby database
    ORA-01103: database name 'orcl' in control file is not 'orcle2'
    Any idea ??

  • Unable to create a duplicat database through rman

    Hi,
    Oracle Version:10.2.0.1
    Operating System:Linux
    Here i am having databae KKK and i need to duplicate that databae to vtldb.I take the backup of the KKK database as
    rman target /
    RMAN>Backup databsase;after that i copied all the bakup sets to my vtldb database in the location '/u01/app/oracle/oradata/vtldb/'.Then i created a new auxiliary channel as
    create auciliary channel as device type disk format '/u01/pp/oracle/oradata/vtldb/%U';Then connecting to my auxiliary databae and getting the following error.
    [oracle@vtlsys3-143 ~]$ rman target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Mar 11 13:30:12 2010
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: KKK (DBID=2526957931)
    RMAN> connect aucxiliary sys@vtldb_rmandup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "auxiliary, catalog, clone, rcvcat, target"
    RMAN-01008: the bad identifier was: aucxiliary
    RMAN-01007: at line 1 column 9 file: standard input
    RMAN> connect auxiliary  sys@vtldb_rmandup
    auxiliary database Password:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04006: error from auxiliary database: ORA-01031: insufficient privilegesI create the passowrd file for VTLDB aslo .
    Can any one please help me how to solve my problem.
    Thanks & Regars,
    Poorna Prasad.

    Hi Anil,
    Thanks for your replays.Now i was able to connect to the database.But i am facing another problem.
    RMAN> list backup;
    RMAN> backup database;
    Starting backup at 11-MAR-10
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=/u01/app/oracle/oradata/kkk/system01.dbf
    channel ORA_DISK_1: starting piece 1 at 11-MAR-10
    channel ORA_DISK_2: starting full datafile backupset
    channel ORA_DISK_2: specifying datafile(s) in backupset
    input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
    input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
    channel ORA_DISK_2: starting piece 1 at 11-MAR-10
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 03/11/2010 16:36:11
    ORA-19504: failed to create file "/u02/rman_bkp/kkk/ora_rbk713378170_s"
    ORA-27038: created file already exists
    Additional information: 1
    channel ORA_DISK_2 disabled, job failed on it will be run on another channel
    channel ORA_DISK_1: finished piece 1 at 11-MAR-10
    piece handle=/u02/rman_bkp/kkk/ora_rbk713378170_s tag=TAG20100311T163610 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
    input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
    channel ORA_DISK_1: starting piece 1 at 11-MAR-10
    channel ORA_DISK_1: finished piece 1 at 11-MAR-10
    piece handle=/u02/rman_bkp/kkk/ora_rbk713378186_s tag=TAG20100311T163610 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00004 name=/u01/app/oracle/oradata/kkk/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 11-MAR-10
    channel ORA_DISK_1: finished piece 1 at 11-MAR-10
    piece handle=/u02/rman_bkp/kkk/ora_rbk713378201_s tag=TAG20100311T163610 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 11-MAR-10
    Starting Control File Autobackup at 11-MAR-10
    piece handle=/u02/rman_bkp/rman_ctlbkp/ora_cfc-2526957931-20100311-03 comment=NONE
    Finished Control File Autobackup at 11-MAR-10
    RMAN> connect auxiliary sys@vtldb
    auxiliary database Password:
    connected to auxiliary database: VTLDB (not mounted)
    RMAN> duplicate target database to vtldb
    2> ;
    Starting Duplicate Db at 11-MAR-10
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=159 devtype=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: sid=157 devtype=DISK
    contents of Memory Script:
       set until scn  557331;
       set newname for datafile  1 to
    "/u01/app/oracle/oradata/vtldb/system01.dbf";
       set newname for datafile  2 to
    "/u01/app/oracle/oradata/vtldb/undotbs01.dbf";
       set newname for datafile  3 to
    "/u01/app/oracle/oradata/vtldb/sysaux01.dbf";
       set newname for datafile  4 to
    "/u01/app/oracle/oradata/vtldb/users01.dbf";
       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
    Starting restore at 11-MAR-10
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 03/11/2010 17:07:11
    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 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 restoreRegards,
    Poorna Prasad.

Maybe you are looking for