Zero downtime migration using rman

=================================

Source
=======

1) Make sure that on going change extract is replicating the data

2) Stop the replicat on the target
3) Take the export backup using rman

OS> RMAN target /

RMAN> backup database plus archivelog ;
4) Copy backup files to destination located in the same location as they were
written on the source
5) Once backup completes, capture SCN to clear datafile fuzziness
6) RMAN> restore database preview summary;
Media recovery start SCN is 34821758
Recovery must be done beyond SCN 34822578 to clear datafile fuzziness
Finished restore at 10-OCT-10
Note for future use the second SCN (34822578) returned from the command, it
appears at the end of the output.
7) Insert few records to source tabled

Target
========

1) Startup the auxilairy instance in nomount stage

2) Make sure the password file and tnsnames.ora is in proper place
3) Create duplicate database. This step will open the database OS> RMAN target
sys/<sys password for source db>@<source database from tnsnames.ora >

RMAN> connect auxiliary /

RMAN> duplicate target database to <databasename> nofilenamecheck until scn
<value returned from RMAN restore database preview summary command> ;
4) From the alert log on the target , we can find the scn at which the database was
opened using 'RESETLOGS'

RESETLOGS after incomplete recovery UNTIL CHANGE 34822578

5) Start replicat

GGSCI > start replicat <rename>, aftercsn <value returned from alert log for
SCN database was recovered to>
7) Verify , if the records inserted on Step 7 is replicated to the target.