Re: Sanity Check

This doesn't really answer your question, but I would have built a standby
on the new hardware and then done a switchover at the time of the actual
migration. Guaranteed no dataloss. Then pull down the old primary/new
standby after you're done and sure all is well.

Finn

On Fri, Oct 10, 2008 at 3:52 PM, Taylor, Chris David <
Chris.Taylor@xxxxxxxxxxxxxxx> wrote:

>  Guys & Gals,
>
> We have a database migration to new hardware tomorrow and this is something
> I was considering doing to save time tomorrow.  I wanted to get a sanity
> check to see if I'm missing anything or have failed to consider anything.
>
> 1.) Restore prod database to the new machine (same name, same paths)
> tonight
> 2.) Shutdown prod database tomorrow and switch logfiles as part of the
> shutdown (shutdown trigger) to generate final archivelogs on old machine
> 3.) Copy archivelogs from old machine after shutdown to new machine
> 4.) Recover <new> prod database on new machine
> 5.) Open <new> prod database on new machine with resetlogs
> 6.) Take a backup of <new> prod database
>
> Do I run any risk of losing transactions in the existing prod database?
>
> Anything I've failed to consider?
>
> Thanks!
>
> *Chris Taylor*
> *Sr. Oracle DBA*
> Ingram Barge Company
> Nashville, TN 37205
> Office: 615-517-3355
> Cell: 615-354-4799
> Email: chris.taylor@xxxxxxxxxxxxxxx
>
>

Other related posts: