This content has been marked as final. Show 3 replies
2-Not necesarily, although once you want to start replicat on the target you should have the files available there. If the replicat on target is stopped already it should not make a difference if this is stopped or not
3-Correct, else it will most liekly fail with row not found when trying to apply a transaction.
I assume you will be using flashback_scn method?
Configure and start the extract processes in the source side
Take an export of that schema using flashback_scn number
Import into the target database
Configure the replicats
Start the replicats after SCN# like start replicat <rep_name>, aftercsn <SCN#>
Thank you NK for reminding us about FLASHBACK_SCN . We would've missed that and it would have caused all those FK errors.
You mentioned about starting replicat with aftercsn clause.
You mean I have to get the SCN of the source using either of the below queries just before I start the expdp of the source tables ?
start replicat <rep_name>, aftercsn <SCN#>
select current_scn from v$database; or select dbms_flashback.get_system_change_number() from dual;
Just follow the setup steps shown in the tutorial: