This is exactly how we migrated a database from 9i to 10g onto a new
server. We had strict uptime requirements for the database. This gave
us the opportunity to perform a switchover to the new server very
quickly (like in an afternoon).
Look at creating the MV's on pre-built tables in your new database.
These are the basic steps:
Create the tables in your new database.
Pick and choose what tables need to be MV'ed. Example: Tables that are
never updated can be moved now (like reference tables).
Create the MV's on the other tables. Refresh them at a schedule that is
convenient for you. It might be once a day or every hour.
Pick the switch-over date. On that day, shut down the application on
the source database. Perform one more MV refresh. Shut down the old
database. Switch your application's database connections to the new
database, start the application and you are on your way.
Hope this helps.
On Behalf Of Yechiel Adar
Sent: Sunday, November 23, 2008 1:47 AM
Subject: Use MV to convert 9i to 10g
Can I use materialized views to copy data from existing 22.214.171.124 database
From windows 32 bit to Linux 64 bit?
I have a 3 TB database that I need to move.
What happened during the first refresh that copy all the data, is the
originating table still available for updates during this time?
I will research the new and open an SR but I want your opinion where
this is practical.