RE: transporting 3 TBs of data to a new database

From: H.TonguÁ YILMAZ <>
Date: Fri, 3 Oct 2008 12:46:32 +0300
Message-ID: <>

I remember myself asking a similar question to the list here.

But first of all you didn't mention details of your Oracle release, source and target databases' OS versions?

There are several limitations(especially related to the datatypes) on Streams based options depending on your release. Please search Metalink for these notes.

If you go for a row-by-row option(data pump or insert into select from kind of migration) then testing for migration's validity and performance and also post migration application performance is important.

So here is a brief summary of our experience: from Hp-Tru 64 to IBM AIX, ~6,5 hours for ~3,8 TB of table data transfer over dblink and plus index builds. And I think even more performance is possible depending on your downtime constraints, performance of this kind of a migration depends highly on your hardware capabilities(network, disk, memory and cpu), configuration of these resources and parallelization of the tasks.

But success of this kind of a migration is highly depending on your tests quality and DBA team's dedication since there are a lot of issues to be checked and handled manually.

For more details of our experience please check my answers to a similar question on OTN forums here:

2008/10/3 FreeLists Mailing List Manager <>

    oracle-l Digest Thu, 02 Oct 2008 Volume: 05 Issue: 271

    Dba DBA schrieb:
> I am on ASM, the group moving the data is not. I think transportable
> tablespaces is the best way to do this. So I have to use RMAN to put

> data in ASM. Is this a copy to an an ASM tablespace? Any idea how
> this works? I am trying to figure out how long this will take. We may

> able to do it in pieces.
> I dont think data pump is good for this.
> I also dont know a good wait to write comma delimitted files out of

> much data to sql load.

Best Regards,

Received on Fri Oct 03 2008 - 04:46:32 CDT

Original text of this message