Materialized Views vs Materialized View Logs

[sjwales]

Been doing some looking into this and haven't been able to find an answer yet.

We're implementing a new application this weekend. During the implementation project, we've had a replicated copy of the database for users to perform ad-hoc queries.

Starting tonight, we're dropping the target 'production' database (which holds the materialized view logs as the source database) in preparation for the load of the real production data over the weekend.

However, they really don't want to have to drop the replicated database (which has the materialized views in it) until Friday.

I was thinking about changing the refresh interval on the target database to be something ridiculous like 14 days away, then dropping the materialized view logs from the source.

Will this work? Since no refresh of data will be required, I'm hoping that the target won't call the source to say "Hey! I need the contents of the MVLogs now please."

Anyone able to offer any insight into this?

Source Database: HPUX 11i, Oracle 9.2.0.2
Target Database: Windows 2000, Oracle 9.2.0.2.1

Thanks
Steve


Steve Wales
stephen.wales@riotinto.com

 

[karluk]

It looks to me as if your strategy should work. The logs are only needed to supported fast refreshes so, if you change the schedule to not do a refresh over the weekend, the fact that they are temporarily missing won't be noticed.

 

[sybaseguru]

Steve,

You should not have a problem as pointed out. I assume that you want to keep the replicate site until the migration is over and you have done a clean cut over. Just set the refresh interval as you suggested and drop the replication over next weekend before any refresh is made.

good luck