Materialized view replication/recovery ...
We're using materialized views for datawarehouse and they're refreshed incrementally using mlogs (Row IDs) on the source database. We've currently set our target database in no-archive log mode, but we're exploring pros & cons on whether we need to backup target materialized view database.
I've a couple of question on DB recovery scenario.
During the middle of the refresh, if the target database crashes and recovered point-in-time, would the refresh continue from the where it was left? Do we need to do a complete refresh again? Similarly, if the source database is recovered point-in time, would it affect the refresh set up? Does the target database need to be reset to the same point-in-time as the recovered source database?
I've a couple of question on DB recovery scenario.
During the middle of the refresh, if the target database crashes and recovered point-in-time, would the refresh continue from the where it was left? Do we need to do a complete refresh again? Similarly, if the source database is recovered point-in time, would it affect the refresh set up? Does the target database need to be reset to the same point-in-time as the recovered source database?
0