Hello,
We are performing a database migration involving DB2 as source and Oracle as target. The migration method is to use GoldenGate and we have tested all necessary production scenarios and passed all of them successfully till now.
We are now discussing on the rollback plan to be adopted for the migration strategy. We thought if proper testing is being done on the migration strategy and the new application/DB stack, why a roll back would required. But production is always production !
Let's say if we adopt reverse sync from Oracle to DB2 after go live, and there by any chance the new stack getting garbage data which is identified in 2 or 3 days after go live, the same will be reflected to DB2 and hence we can't roll back to the earlier stack now which again will consist of the same garbage data.
What would be the rollback plan that can be adopted which can mitigate such risks? Let me know for additional details.
Thanks!