RE: Migrate databases to new servers and storage

From: Uzzell, Stephan <SUzzell_at_MICROS.COM>
Date: Thu, 16 Oct 2014 00:08:35 +0000
Message-ID: <d25cd34aad7f4c9a9c362f3f1caf1493_at_USMAIL2K1301.us.Micros.int>

Include me in the group that doesn't understand what the consultants are proposing... You cannot recover a new database with archivelogs from the old database, nor can you apply archivelogs to a export.

I hate to say "it depends" but it depends. Your best method is going to depend on your technology stack. Are these all on SAN storage? On ASM? We've been using a technique of shutting down on the old hosts, swinging the LUNs to the new servers, starting them up over there (of course, we've been adding Oracle upgrades to the process, but...). If these are SAN/ASM, that may be an easy approach.

If not on SAN/ASM, I'd say the standby approach sounds like your best option.

[Oracle | Micros]<http://www.oracle.com/> Stephan Uzzell | Database Administrator | HGBU Cloud Operations Mobile: +1 443.864.1725
Oracle Hospitality
Swarthmore, PA | US
[cid:image002.gif_at_01CFDD84.DCD06460]<http://www.oracle.com/commitment>

Oracle is committed to developing practices and products that help protect the environment

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Sandra Becker Sent: Wednesday, 15 October, 2014 18:09
To: oracle-l
Subject: Migrate databases to new servers and storage

Current Environment: Solaris 10, EE 9.2 through 11.2 New Environment: Solaris 11, no change to the Oracle versions Databases range in size from 8G to 3T.

Over the next 5 months we will be moving our production databases to new servers and storage. The consultants working with use (no DBAs) have proposed the following method for moving the databases:

1.  create new databases on the new servers
2.  create an export of the current database
3.  import into the new database
4.  copy archivelogs to the new server
5.  use RMAN to recover the new database
6.  Consultants didn't address this - what do we do with standby databases?  Not every database has a standby.

This is really high level, but is this the best way to migrate the databases? For the smaller databases that do not have a lot of DML or a standby, I don't see this as problematic. Am I mistaken? What have others done? Our downtime window for any one database is 4 hours. The other oracle DBA and I have considered two other possible options: 1. import through a dblink
2. create a standby on the new server and switch it to primary during the downtime window Are these really valid options for us to consider? Appreciate your suggestions and thoughts.

--
Sandy
GHX





--
http://www.freelists.org/webpage/oracle-l

Received on Thu Oct 16 2014 - 02:08:35 CEST