Thursday, April 25, 2013

Resume failed rman duplicate

RMAN automatically optimizes a DUPLICATE command that is a repeat of a previously failed DUPLICATE command. The repeat DUPLICATE command notices which datafiles were successfully copied earlier and does not copy them again. This applies to all forms of duplication, whether they are backup-based (with or without a target connection) or active database duplication. The automatic optimization of the DUPLICATE command can be especially useful when a failure occurs during the duplication of very large databases.
If a DUPLICATE operation fails, you need only run the DUPLICATE comand again, using the same parameters contained in the original DUPLICATEcommand. 

The second DUPLICATE operation locates the datafiles that were successfully duplicated by the initial DUPLICATE command. Restores only the missing or incomplete datafiles, thereby avoiding re-copying and restoring all the datafiles.

Before you attempt to resume a failed DUPLICATE operation, you must reset the auxiliary instance to NOMOUNT mode. One way to do this is to exit RMAN, use SQL*Plus to reset the auxiliary instance to NOMOUNT mode, start RMAN and then repeat the DUPLICATE command. If you do not want RMAN to automatically recover from a failed DUPLICATE operation, specify the keyword NORESUME to disable the functionality. Using the keywordNORESUME in the first invocation of DUPLICATE prevents a subsequentDUPLICATE command for the new database from using this automatic optimization.

Monday, April 8, 2013

Cloning Oracle Database Without Connecting Catalog and Target using rman

Cloning oracle database without accessing target database or rman catalog. Only we need is a full rman  backup including controlfile and parameter file. Below given is the step to achieve this.

Step 1:Take Backup of Target database to a specific destination.

run {
allocate channel t1 type disk;
backup current controlfile format '/tem/bck/ctl_%d_%u_%s';
backup database format '/tem/bck/data_%d_%u_%s';
backup archivelog all format '/temp/bck/arch_%d_%u_%s';
release channel t1;