Oracle Standby Database Creation using RMAN Duplicate and Error Handling

Primary
RMAN> run
{
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\Test_BKP_200216\autobackup_control_file%F';
 allocate channel bkp1 device type disk;
allocate channel bkp2 device type disk;
allocate channel bkp3 device type disk;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT 'C:\Test_BKP_200216\databasefiles_%d_%u_%s_%T';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT 'C:\Test_BKP_200216\archivelogs_%d_%u_%s_%T';
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT 'C:\Test_BKP_200216\controlfile_%d_%u_%s_%T';
release channel bkp1;
release channel bkp2;
release channel bkp3;
}

Output:
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\RMAN_Backup\Test\autobackup_control_file%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\Test_BKP_200216\autobackup_control_file%F';
new RMAN configuration parameters are successfully stored

released channel: ORA_DISK_1
allocated channel: bkp1
channel bkp1: SID=96 device type=DISK

allocated channel: bkp2
channel bkp2: SID=221 device type=DISK

allocated channel: bkp3
channel bkp3: SID=213 device type=DISK

Starting backup at 20-FEB-16
channel bkp1: starting compressed full datafile backup set
channel bkp1: specifying datafile(s) in backup set
input datafile file number=00007 name=E:\ORACLE\ORADATA\TESTPRD\CBNRTPRD_DTL_DAT.DBF-
-----
------
Starting backup at 20-FEB-16
current log archived
released channel: bkp1
released channel: bkp2
released channel: bkp3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/20/2016 05:55:01
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file F:\ORACLE_ARCHIVES\TESTPRD\ARCH_DR_TESTPRD_1_31972_900885765.ARC
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.

Stand BY
duplicate target database for standby dorecover nofilenamecheck;

Output
--------------
--------------
contents of Memory Script:
{
   set until scn  938201952292;
   recover
   standby
   clone database
    delete archivelog
   ;
}
executing Memory Script

executing command: SET until clause

Starting recover at 20-FEB-16
using channel ORA_AUX_DISK_1

starting media recovery

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/20/2016 15:04:46
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 46840 and start
ing SCN of 938201950187 found to restore

Conclusion - In spite  of all above errors while taking backup and restoration, database recovery was completed with help of manual registration of missing logfiles. 

Action After Getting Above Error 
Copy archive log files from production to standby and then register files manually

SQL>alter database register logfile 'F:\oracle_archives\testprd\ARCH_DR_TESTPRD_1_46465_900885765.ARC';

Comments