RE: Export (exp) or Datapump (expdp)
Date: Fri, 2 Aug 2013 20:00:55 +0000
Message-ID: <6837D1E9EB637E41AF54220483D53D370626B498_at_exchm-omf-23.exelonds.com>
Or do a CTAS across a db link using parallel DML (destination) nologging and parallel query (source) and save UNDO. Create indexes in parallel mode nologging.
Thanks,
Finn
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tim Gorman
Sent: Friday, August 02, 2013 3:44 PM
To: oracle-l_at_freelists.org
Subject: Re: Export (exp) or Datapump (expdp)
Either EXPDP from the source database, or IMPDP from the destination database, using the NETWORK_LINK and PARALLEL parameters. Prevents time, space, and I/Os from being wasted on writing to and reading from intermediate ".dmp" files.
On 8/2/2013 1:37 PM, Bala wrote:
> I have a requirement to copy 80 mllion rows table from PROD to DEV.
> This table is 28 GB in size, has 4 indexes built on its columns.
>
> 11gR2 (11.2.0.3), Linux Redhat 6 environment.
>
> What would be the most optimal way to do it -- use traditional export
> or datapump (expdp) ,any insight will be greatly appreciated.
>
> Thank you all for your time.
>
-- http://www.freelists.org/webpage/oracle-l This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. -EXCIP -- http://www.freelists.org/webpage/oracle-lReceived on Fri Aug 02 2013 - 22:00:55 CEST