Hi,
I am doing the cloning from http://ermanarslan.blogspot.com/2014/07/ebs-122-cloning-real-life-example.html when I am doing I am getting the error below: RMAN> duplicate target database to "UAT" BACKUP LOCATION '/backup/PROD/backupset'; Starting Duplicate Db at 13-JUL-16 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 07/13/2016 17:44:28 RMAN-05501: aborting duplication of target database RMAN-05579: CONTROLFILE backup not found in /backup/PROD/backupset The backup sets are in the directory /backup/PROD/backupsets as shown below: baclupsets.PNG Can you please advise Thanks, Roshan |
Administrator
|
Give the full location of your backup ->
'/backup/PROD/backupset/<directory_name>' and retry |
I am getting same error:
RMAN> duplicate target database to "UAT" BACKUP LOCATION '/backup/PROD/backupset/2016_07_12/'; Starting Duplicate Db at 13-JUL-16 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 07/13/2016 19:18:25 RMAN-05501: aborting duplication of target database RMAN-05579: CONTROLFILE backup not found in /backup/PROD/backupset/2016_07_12/ |
This post was updated on .
I set the dbid first
set dbid=293518444 restore controlfile from autobackup ; Now I am getting: MAN> duplicate target database to "UAT" BACKUP LOCATION '/backup/PROD/backupset/'; Starting Duplicate Db at 13-JUL-16 using target database control file instead of recovery catalog allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=7503 device type=DISK allocated channel: ORA_AUX_DISK_2 channel ORA_AUX_DISK_2: SID=8754 device type=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 07/13/2016 19:39:55 RMAN-05501: aborting duplication of target database RMAN-05513: cannot duplicate, control file is not current or standby |
Administrator
|
Do you have controlfile autobackup on?
check with rman>show all and if autobackup is not enabled ; then retake the backup after enabling it. RMAN> Configure controlfile autobackup on; RMAN> backup database plus archivelog; |
I set the dbid first
set dbid=293518444 restore controlfile from autobackup ; Now I am getting: MAN> duplicate target database to "UAT" BACKUP LOCATION '/backup/PROD/backupset/'; Starting Duplicate Db at 13-JUL-16 using target database control file instead of recovery catalog allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=7503 device type=DISK allocated channel: ORA_AUX_DISK_2 channel ORA_AUX_DISK_2: SID=8754 device type=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 07/13/2016 19:39:55 RMAN-05501: aborting duplication of target database RMAN-05513: cannot duplicate, control file is not current or standby |
I ran the following command:
SQL> select CONTROLFILE_TYPE from v$database; CONTROL ------- BACKUP |
I am checking doc 1450622.1
Do I need to modify my listener.ora? The hostname is different from target |
Administrator
|
send me the output of rman > show all (from source)
send me the ls -al output of "/backup/PROD/backupset/2016_07_12/" |
This post was updated on .
RMAN> connect target /
connected to target database: PROD (DBID=293518444) RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name PROD are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2; 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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA D TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 4 TIMES TO 'SBT_TAPE'; CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/oracle/PROD/db/11.2.0/dbs/snapcf_PR OD.f'; # default [orauat@erpuat backupset]$ ls -al 2016_07_12/ total 19060380 drwxrwxrwx 1 root root 4096 Jul 12 21:51 . drwxrwxrwx 1 root root 4096 Jul 12 04:09 .. -rwxrwxrwx 1 root root 473882624 Jul 12 21:52 o1_mf_annnn_AFTERNOON_ARCHIVED_0_crbcddmz_.bkp -rwxrwxrwx 1 root root 154521088 Jul 12 21:51 o1_mf_annnn_AFTERNOON_ARCHIVED_0_crbcddno_.bkp -rwxrwxrwx 1 root root 197863424 Jul 12 04:10 o1_mf_annnn_ERP_DAILY_BACKUP_071_cr8f6dv8_.bkp -rwxrwxrwx 1 root root 6060032 Jul 12 12:22 o1_mf_annnn_MIDDAY_ARCHIVED_LO_0_cr9b2gt4_.bkp -rwxrwxrwx 1 root root 441806848 Jul 12 12:24 o1_mf_annnn_MIDDAY_ARCHIVED_LO_0_cr9b2gwy_.bkp -rwxrwxrwx 1 root root 8152350720 Jul 12 03:57 o1_mf_nnnd0_ERP_DAILY_BACKUP_071_cr898c6v_.bkp -rwxrwxrwx 1 root root 10091331584 Jul 12 04:09 o1_mf_nnnd0_ERP_DAILY_BACKUP_071_cr898c7j_.bkp [orauat@erpuat backupset]$ |
Administrator
|
What is the output of the following; (from source) 2016-07-13 19:50 GMT+03:00 Roshan [via Erman Arslan's Oracle Forum] <[hidden email]>: RMAN> show all Erman Arslan Applications and Database Operations Manager Oracle Certified Expert Certified Exadata Administrator Certified Linux Administrator Author for Apress MBA Blog: ermanarslan.blogspot.com Forum: http://ermanarslan.blogspot.com/p/forum.html
M: 05301567803 |
I managed to connect to target:
connect target sys/manager@PROD then I connected as auxiliary / when I issuing the duplicate command: DUPLICATE DATABASE TO UAT BACKUP LOCATION '/backup/PROD/autobackup/2016_07_12/' I am getting the archivelog error: rmanLog4.txt I cannot startup mount to make the database archivelog mode Regards, ROshan |
Administrator
|
Roshan, It seems, you changed your duplication method. Firstly, you were doing : "Backup-Based Duplication Without a Target Connection or Recovery Catalog Connection" Now , you are doing :"Backup-Based Duplication with a Target Connection" In this case when performing backup-based duplication with a target connection, RMAN obtains metadata from the control file. This is from docs.oracle: Ensure that auxiliary channels on the destination host can access all data file backups and archived redo log files (required to restore and recover the duplicate database to the desired point in time). If not, duplication fails. The archived redo log files can be available either as image copies or backup sets. 2016-07-14 11:03 GMT+03:00 Roshan [via Erman Arslan's Oracle Forum] <[hidden email]>: I managed to connect to target: Erman Arslan Applications and Database Operations Manager Oracle Certified Expert Certified Exadata Administrator Certified Linux Administrator Author for Apress MBA Blog: ermanarslan.blogspot.com Forum: http://ermanarslan.blogspot.com/p/forum.html
M: 05301567803 |
Hi,
it's working now. I only connected to auxiliary / the spfile I deleted. In the pfile I specified the dull path of backupset and now it is working. Thanks |
Administrator
|
What do you mean by "In the pfile I specified the dull path of backupset and now it is working. "?
|
I removed the spfile.
In the pfile , for parameter db_recovery_file_dest I input the full path of backup of production - /backup/PROD/backupset/2016-07-14/ then I connected only to auxiliary / then I ran the duplicate command and it worked |
Administrator
|
Okay. Then your db_recovery_file_dest parameter in the duplicated environment was wrong..
This means: there is nothing wrong in this blogpost : http://ermanarslan.blogspot.com/2014/07/ebs-122-cloning-real-life-example.html |
Administrator
|
db_recovery_file_dest seems so unrelated to me. You are already giving the
backup location in your duplicate command : duplicate target database to "UAT" BACKUP LOCATION '/backup/PROD/backupset' What else did you have in your spfile? List all the things that you have done one by one for a correct execution, and let's find what the real cause was. |
Free forum by Nabble | Edit this page |