This error was because in the original environment Standby Database was running in MAXIMUM AVAILABILITY mode and it needs a valid destination for LOG_ARCHIVE_DEST_2. Finished restore at 18-APR-12, Starting recover at 18-APR-12 The farthest that RMAN can go in recovery of the duplicate database is the most recent redo log archived by the target database. All backups and archived redo logs used for creating and recovering the duplicate database, however, must be accessible by the server session on the duplicate host. RMAN> catalog backuppiece /u01/app/oracle/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp; using target database control file instead of recovery catalog input archived log thread=1 sequence=1312 RECID=388 STAMP=780914872 /u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1316_7ryyjztx_.arc no longer input datafile file number=00005 name=/u01/oradata/HDESK11G/example01.dbf using channel ORA_DISK_1 input datafile file number=00008 name=/u01/oradata/HDESK11G/testme01.dbf Fixed Size 2215064 bytes If the primary database is damaged or destroyed, then you can perform failover to the standby database and transform it into the new primary database. /u01/app/oracle/oradata/CLONEDB/example01.dbf Oracle Data Guard Concepts and Administration, "Preparing the RMAN DUPLICATE Auxiliary Instance: Basic Steps", Oracle Database Backup and Recovery Reference. Copyright (c) 1982, 2009, Oracle and/or its affiliates. input archived log thread=1 sequence=1305 RECID=381 STAMP=780913812 All rights reserved. SQL> alter database set standby database to maximize performance; SQL> alter database backup controlfile to trace; Copy trace file to target site and edit as required, Create a test table as SYSTEM (just to test the process). SQL> startup nomount SQL> recover database until cancel using backup controlfile; ORA-00279: change 23286334 generated at 04/18/2012 10:51:31 needed for thread 1 Manually transfer the backups from the primary host to the duplicate host at a new location. ORA-00280: change 23397491 for thread 1 is in sequence #1316 input archived log thread=1 sequence=1300 RECID=376 STAMP=780913484 input datafile file number=00007 name=/u01/oradata/HDESK11G/common_data01.dbf You can create the duplicate database in a new host. From 11G onwards controlfile backups are interchangible. output file name=/u01/app/oracle/oradata/HDESK11G/control01.ctl channel ORA_DISK_1: restore complete, elapsed time: 00:04:35 When using disk backups, you can accomplish this goal in any of the following ways: Manually transfer the backups from the primary host to the remote host to an identical path. o1_mf_1_1316_7ryyjztx_.arc 100% 359KB 358.5KB/s 00:00, Startup nomount note init.ora file is having new database name, [oracle@kens-orasql-001-dev dbs]$ export ORACLE_SID=CLONEDB A duplicate database is a copy of a target database that you can run independently for a variety of purposes. ORA-00289: suggestion : Allrightsreserved. /u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1314_7ryx9660_.arc The principal work of the duplication is performed by the auxiliary channel, which starts a server session on the duplicate host. Allocate at least one auxiliary channel on the auxiliary instance. /u01/app/oracle/oradata/CLONEDB/sysaux01.dbf connected to target database: HDESK11G (DBID=1866661199, not open). Run the CATALOG command to add these copies to the RMAN repository at the duplicate host. channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/HDESK11G/undotbs101.dbf input archived log thread=1 sequence=1306 RECID=382 STAMP=780913822 The duplicate database can be identical to the target database or contain only a subset of the tablespaces in the target database. Finished Control File and SPFILE Autobackup at 18-APR-12. Finished backup at 18-APR-12, Starting backup at 18-APR-12 using target database control file instead of recovery catalog channel ORA_DISK_1: starting compressed full datafile backup set total 843700 channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/HDESK11G/users01.dbf needed for this recovery, Specify log: {=suggested | filename | AUTO | CANCEL} o1_mf_1_1314_7ryx9660_.arc 100% 387KB 387.0KB/s 00:00 Required fields are marked *. channel ORA_DISK_1: finished piece 1 at 18-APR-12 For example, if the backups are in /dsk1/bkp on the target host, then you might transfer them to /dsk2/dup on the duplicate host. scp all the data files to the target server channel ORA_DISK_1: backup set complete, elapsed time: 00:05:15 Here are a few examples of using the physical Standby database in a Data Guard environment to create a clone of the primary production database. Enter password: regards Total System Global Area 2137886720 bytes channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/HDESK11G/system01.dbf /u01/app/oracle/oradata/CLONEDB/redo03.log Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00280: change 23395781 for thread 1 is in sequence #1314 Your email address will not be published. Enter password: Database Buffers 1577058304 bytes channel ORA_DISK_1: specifying datafile(s) in backup set input archived log thread=1 sequence=1308 RECID=384 STAMP=780914245 To prepare for database duplication, first create an auxiliary instance as described in "Preparing the RMAN DUPLICATE Auxiliary Instance: Basic Steps". channel ORA_DISK_1: failover to piece handle=/u01/app/oracle/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp tag=TAG20120418T105342 In some cases, you can set the duplicate database DB_NAME differently from the target database DB_NAME. -rw-r 1 oracle oinstall 113127424 Apr 19 10:08 o1_mf_1_1313_7rywxhl0_.arc Finished backup at 18-APR-12, Starting backup at 18-APR-12 ORA-00280: change 23397950 for thread 1 is in sequence #1317 input archived log thread=1 sequence=1309 RECID=386 STAMP=780914858 You can exclude tablespaces from the duplicate database with the SKIP TABLESPACE clause. channel ORA_DISK_1: starting piece 1 at 18-APR-12 Media recovery complete. LGWR: Minimum of 1 LGWR standby database required ORA-00278: log file A common DBA task is to perform regular clones and database refreshes of the production database for the purpose of setting up training or test or development environments. /u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1314_7ryx9660_.arc no longer I'm HOOKED! For the duplication to work, you must connect RMAN to both the target (primary) database and an auxiliary instance started in NOMOUNT mode. input datafile file number=00001 name=/u01/oradata/HDESK11G/system01.dbf Variable Size 553649000 bytes As a routine I check your blog every morning. ORA-00279: change 23396254 generated at 04/19/2012 10:15:02 needed for thread 1 ORA-00289: suggestion : Ensure last archive log file is present after the alter database end backup command is issues on primary, [oracle@kens-orasql-002 2012_04_19]$ scp -rp *.arch oracle@kens-orasql-001-dev:/u01/app/oracle/oradata/CLONEDB/arch [oracle@kens-orasql-001-dev oracle]$ rman target /, Recovery Manager: Release 11.2.0.1.0 Production on Wed Apr 18 11:15:00 2012. channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 You can exclude any tablespace except the SYSTEM tablespace or tablespaces containing rollback or undo segments. SQL> create table test_me using channel ORA_DISK_1 Redo Buffers 4964352 bytes But control file which was restored belonged to a Data Guard Primary database (even though we took it from Standby) this is the difference in 11g. /u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1313_7rywxhl0_.arc ORA-00278: log file When using tape backups, you must make the tapes containing the backups accessible to the remote node. Gavin, you've done it again! RMAN> restore controlfile from /u01/app/oracle/ o1_mf_s_780922291_7rwchkow_.bkp; Starting restore at 18-APR-12 rac 11gr2 installation rdbms Thanks for the info! /u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1315_7ryy5322_.arc A duplicate database is distinct from a standby database, although both types of databases are created with the DUPLICATE command. ======================================== piece handle=/u01/oradata/HDESK11G/FRA/HDESK11G2/backupset/2012_04_18/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp tag=TAG20120418T105342 comment=NONE This option is possible because RMAN gives the duplicate database a new, unique DBID during duplication. Oracle GoldenGate and Oracle 12c Online Training Commencing January 2017, Now an Oracle 12c Certified Master Database Cloud Administrator, Presenting at AUSOUG and AIOUG Conferences in November, Performing a database clone using a Data Guard physical standby database, Oracle Cloud Marketplace GoldenGate Classic Environment, Oracle GoldenGate on Oracle Cloud Marketplace (Part 3), Oracle GoldenGate on Oracle Cloud Marketplace (Part 2), Data migration to Autonomous Database using MV2ADB, Migrate data in real-time from OCI Classic to OCI using MV2ADB and Oracle Cloud Marketplace GoldenGate. Duplicating a database with RMAN involves a number of prerequisites and restrictions. In the first example we use RMAN to perform the backup and restore and in the second example we are using OS commands to just copy files ONLINE from Standby host to the target host. If the duplicate database is in a different Oracle home from the target database, then the DB_NAME setting for the duplicate database must be unique among databases in its Oracle home. channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/HDESK11G/example01.dbf ON STANDBY -rw-r 1 oracle oinstall 396288 Apr 19 10:15 o1_mf_1_1314_7ryx9660_.arc ========================================================== channel ORA_DISK_1: specifying archived log(s) in backup set [oracle@kens-orasql-001-dev dbs]$ sqlplus sys as sysdba, SQL*Plus: Release 11.2.0.1.0 Production on Thu Apr 19 10:48:47 2012. [oracle@kens-orasql-002 HDESK11G]$ scp -rp *.dbf oracle@kens-orasql-001-dev:/u01/app/oracle/oradata/CLONEDB For example, the NFS mount point for both hosts could be /home/file_server. Redo Buffers 4964352 bytes, Apply the archive log files and recover the database, SQL> !ls -lrt /u01/app/oracle/oradata/CLONEDB/arch/ ORA-16072: a minimum of one standby database destination is required channel ORA_DISK_1: starting compressed archived log backup set LGWR (ospid: 7926): terminating the instance due to error 16072 Finished backup at 18-APR-12, Starting Control File and SPFILE Autobackup at 18-APR-12 ORA-00279: change 23395781 generated at 04/19/2012 10:08:47 needed for thread 1 input archived log thread=1 sequence=1304 RECID=380 STAMP=780913805 As part of the duplicating operation, RMAN automates the following steps: Creates a control file for the duplicate database, Restores the target datafiles to the duplicate database and performs incomplete recovery by using all available incremental backups and archived redo logs, Shuts down and starts the auxiliary instance (refer to "Task 4: Start the Auxiliary Instance" for issues relating to client-side versus server-side initialization parameter files), Opens the duplicate database with the RESETLOGS option after incomplete recovery to create the online redo logs (except when running DUPLICATE FOR STANDBY, in which case RMAN does not open the database), Generates a new, unique DBID for the duplicate database (except when you create a standby database with DUPLICATE FOR STANDBY, in which case RMAN does not create a unique DBID).