RE: Sanity Check
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
- To: "Chris.Taylor@xxxxxxxxxxxxxxx" <Chris.Taylor@xxxxxxxxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 10 Oct 2008 16:31:48 -0400
Chris,
To be sure, after copying all the archivelogs from the old server to the new
server and applying all of them, take copies of the online redo logs, and apply
them in the recovery process as well. This will guarantee no data loss.
So, set up copy of prod on new hardware. Start copying archive logs from prod
to copy on new hardware and applying. At cut over time, shutdown prod, copy
remaining archive logs, apply them. Then copy on-line redo from prod over to
new hardware, and apply them as if they were archived logs (Oracle will not
know the difference). That will guarantee every last transaction will be
applied to the new database. Then just open w/ resetlogs and be on your way.
Hope that helps,
-Mark
--
Mark J. Bobak
Senior Database Administrator, System & Product Technologies
ProQuest
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059 or +1.800.521.0600 x 4059
mark.bobak@xxxxxxxxxxxx<mailto:mark.bobak@xxxxxxxxxxxxxxx>
www.proquest.com<http://www.proquest.com>
www.csa.com<http://www.csa.com>
ProQuest...Start here.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Taylor, Chris David
Sent: Friday, October 10, 2008 3:53 PM
To: ORACLE-L
Subject: Sanity Check
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<mailto:chris.taylor@xxxxxxxxxxxxxxx>
Other related posts:
