Printable View
Don't know your hardware conf and bandwidth you have but I don't think you can export then move and import the database in the new machine with in your 3 hours window. How about testing after the mogration As slimdave mentioned ask the users to sign for the response time and accuracy of the results. It is very important to check in the Migrations. I have a very bad experience with response time after the migration.
vbadba
Hi pando,Quote:
Originally posted by pando
Hmm I wonder what hardware can do "platform swith"
If you use db link or copy with multiple sessions and if you have slower disks that will be a problem
hi all,
we are using a HP Superdome server (24 CPU 32 GB RAM) and the storage is on emc SAN.
We currently migrated a database on the same server of 225GB in 4 Hours using PL/SQl scripts with mainly using db_links . So i am being a bit optimistic that using copy i might just be able to achieve the result on time.
the scripts are all tested, so the factor of any in-consistency creeping in is very minor, but still we do have regular verification scripts which are run after the migrations.
errrr export / import 300gb in 3 hours...? when that happens my dream will come true :oQuote:
Originally posted by vbadba
Don't know your hardware conf and bandwidth you have but I don't think you can export then move and import the database in the new machine with in your 3 hours window. How about testing after the mogration As slimdave mentioned ask the users to sign for the response time and accuracy of the results. It is very important to check in the Migrations. I have a very bad experience with response time after the migration.
vbadba
what I mean is some hardware clonign mechanism, like snapshots (but AFIAK that is for same OS)Quote:
Originally posted by vbadba
Hi pando,
If you use db link or copy with multiple sessions and if you have slower disks that will be a problem
we are using a HP Superdome server (24 CPU 32 GB RAM) and the storage is on emc SAN.
We currently migrated a database on the same server of 225GB in 4 Hours using PL/SQl scripts with mainly using db_links . So i am being a bit optimistic that using copy i might just be able to achieve the result on time.
the scripts are all tested, so the factor of any in-consistency creeping in is very minor, but still we do have regular verification scripts which are run after the migrations.
db link + insert /*+ APPEND */ is faster than copy
MAN, you can do it with in 3 hours.
'specially with the tables set to nologging, ofcourseQuote:
Originally posted by pando
db link + insert /*+ APPEND */ is faster than copy