I did suggest using transportable tablespaces to move the data around as it’s a lot less manual work and fairly fast. Having said that, the migration strategy should include going back from 11g to 9i as well (in the event of a back-out) and I’m not entirely sure we would be able to do that (downgrade going from 11g -> 9i) with transportable tablespaces. Unfortunately the client doesn’t have the appropriate licensing to use golden gate or data guard.For sure TTS would be faster than expdp/impdp. But TTS you have check the database and make sure the TRANSPORT_SET_CHECK passes for all included tablespaces.
I was also thinking of using standard physical standby which should be fine as far as licensing goes for the client; however, do we still have to manually move the data to the new database 1st and then synch up the two databases? Also how would this work as a backout strategy if we need to revert back to 9i?Data guard is another better solution but should not you be thinking of using Logical Standby Database?
The actual production cut over for the database from one data center to the other is likely not expected to go longer then 12-15 hours I imagine as we may only get a 24 hour window, but we need to complete in half the time because the other half might well be reserved for backout, other testing, ..etc.For roll-back why do you need half the downtime windows. You are on solaris, should not you be able to take the snapshot of the zone and keep it. If rollback required, just put the image back.
and after say 48 hrs we dicover something seriously going wrongI Would be very keen to know, what you think that could go wrong after 48 Hours of system being live?
11g wrote:I've seen people not notice stuff wrong for years. Hey, if the computer says it, it has to be right, eh?and after say 48 hrs we dicover something seriously going wrongI Would be very keen to know, what you think that could go wrong after 48 Hours of system being live?
Don't you test application system with new database before you do the production?
If you do not know the worst which could wrong then you will not be able to have a rollback solution for it.
and after say 48 hrs we dicover something seriously going wrong and we do want to rollbackUnless you can license the appropriate technology this is a no-go in my opinion.