Re: Best way to move the modified data after upgrade

Chetan,

On a previous project we used Quest's Shareplex to perform a similar migration with almost no downtime. The high-level steps were something like this:

• start shareplex capture
• take hot backup of the original db
• build the new db, version 8.1.x
• restore the hot backup to the new db
• upgrade the new db to 9.2.x
• start applying captured DML to the new db
• once the new db is near in-sync with the old db, shutdown the old db
• apply remaining DML to new db (should take a few seconds/minutes)
• switch over applications to point to the new db

Mike

Chindarkar, Chetan (CONS FIN , Contractor) wrote:
> Kindly read the whole scenario and let me know your views.
>
> (1) What we have ?
>
> * Three db instances on the same machine.
> * Two of the instances are on 8.1.7.4
> * One of the instance is on 8.1.6.0
> * Oracle as well as O/S is running on 32-bit.
> * Database is running in archivelog mode.
> * The current box is Sun SPARK E6500.
> * Use BCV backup solutions with Veritas NetBackup for tape integration.
> * The production server (E6500) and the backup server both are
> physically located in Ohio.
> * The total db size is 1.5 TB.
>
> (2) What we are going to do ?
>
> * Migrate to a new E12K server.
> * Migrate all three instances to 9.2.0.4
> * Install Oracle on top of 64-bit Sun Solaris 2.9 version.
> * Install 64-bit Oracle software on top of it.
> * The new server is supposed to be located in Arizona.
>
> (3) How we are going to do ?
>
> * Shut down all three instances on the production server.
> * Take the backup on the backup server.
> * Copy the data on to tape.
> * Ship the tapes over to Arizona where the new E12K box resides.
> * Copy all the data from tape on to the new E12K.
> * Upgrade all three instances on the new E12K as mentioned above on
> DAY1.
> * Back up all the data locally.
> * Now it takes around 2 days to ship all the tapes are shipped to
> Arizona and then copy the data over to new E12K. During this time
> the users are still accessing the production server in Mason. Also
> the etl jobs are updating/inserting/deleting data from this server
> in those two days.
>
> (4) Whether this is possible ?
>
> * Now lets say we want to apply just the changed data from DAY1 till
> DAY3 is there any way I can do it ? The only other option we have
> at this moment is to run all the jobs against the newly configured
> E12K. (I guess the answer is NO, but just wanted to confirm with u
> all)
>
> ----------------------------------------------------------------------------------------------------------------------
>
>
> Thanks, Chetan
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Mike Spalinger
  INET: Michael.Spalinger_at_Sun.COM

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).