Moving Database from Dg Unix to HP Ux

First off, migrating a 300G database in three hours is quite a challange. Even if you could move the data that fast (which you can't), that wouldn't give you any time to perform any checks on the imported data. Pure suicide.

That being said, somebody in this forum came up with an idea to use Quest Shareplex and setup replication between two different platforms. I think I remember seeing that it worked and the switchover time was minimal. However, Shareplex is not cheap, especially if you are looking at using it for a limited time.

Quote:

---

Originally posted by marist89
First off, migrating a 300G database in three hours is quite a challange. Even if you could move the data that fast (which you can't), that wouldn't give you any time to perform any checks on the imported data. Pure suicide.

That being said, somebody in this forum came up with an idea to use Quest Shareplex and setup replication between two different platforms. I think I remember seeing that it worked and the switchover time was minimal. However, Shareplex is not cheap, especially if you are looking at using it for a limited time.

---

In 10g you can clone via RMAN from one OS platform to another. And RMAN cloning is the fastest method!

Quote:

---

COPY the data using COPY command & and you can do simulateously in N sessions..when data is copied switch over the DBs and change tns entries in Global Tns path..will that require 3 hour dowtime?

---

Just out of curiosity...you talking about OS copy or SQL copy?

Also, I'm thinking there's no way he's going to be able to get that amount of data copied over and up and running in three hours. Think about it gentlemen a 100 gig per hour. Your managemnt needs to step back and rethink thier acceptable down time. Geeesh you don't even have any room for a fudge factor with that time.

What I would suggest in this case since time is of the esscence (for switch over purposes), would be to create a standby database from your existing prod on your new HP box. Then when it's time to push the button simply let it fail over to the new box. That way depending on the way you've setup your standby your down time could be very minumal.

Thoughts??

Oracle Standby across platforms? I'm not sure that would work. Maybe a logical standby. Definitely replication would work, but there are limitations on replication...

OS has to be the same for physical standby database. And this being 8.1.6 system, logical standby is not an option (and btw, logical standby requires same OS on both sides too).

What is your new hardware configuration and Storage type? you can do only 300gb data move in 3 hours, but it is depending up on your hardware conf.

Asa generic point, which may be obvious, try and get as much done as you can prior to the "live" switchover. This means users, tabelspaces, tables, ndexes, contraints, grants etc.. sequences will have to be reset at the time of switchover, but that's not too much of a challenge.

If you can find data that is static, then migrate that beforehand. For data that will only change "a little" you can consider auditing changes to the tables, migrating the table data, then migrating changes only at the time of switchover.

Also, you'l want al your constraints disabled and indexes unusable at the time you switchover the system. Indexes can be rebuilt parallel & nologging in multiple sessions (for each table, rebuild all the indexes at the same time using multiple sessions to gain the advantage of having table data in the block buffers). If confidence is high, then constraints can be reenabled with the novalidate option.

Oh also, for the love of God do at least two test runs prior to the live switchover, with the same people running the process as for the final switchover, and thoroughly document the timings, processes, results, and get the user community to sign something to say that the result is correct.

Then, stick to the documented procedure for the final run. Partly, it'll tell you whether you can make the three hour window, and whether you really are going to in the live event.

Quote:

---

Originally posted by jmodic
OS has to be the same for physical standby database. And this being 8.1.6 system, logical standby is not an option (and btw, logical standby requires same OS on both sides too).

---

ohhh yea that's right I forgot about that. Good call!

Quote:

---

Originally posted by Chandra
What is your new hardware configuration and Storage type? you can do only 300gb data move in 3 hours, but it is depending up on your hardware conf.

---

Hmm I wonder what hardware can do "platform swith"