Re: TTS Self-contained restriction workaround

We tried it on the Test DB and it took 8 hrs. Test DB is 3TB vs Prod which is 170TB. Haven't tried in Prod yet.

> On Jun 27, 2016, at 9:28 AM, Powell, Mark <mark.powell2_at_hpe.com> wrote:
>
> Why would it take several hours just to extract the metadata, which is nothing more than the table associated object DDL, that is create table, create index, create trigger, etc... DDL? Have you actually timed a metadata only export of the target objects?
>
> ________________________________
> From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Deepak Sharma <dmarc-noreply_at_freelists.org>
> Sent: Friday, June 24, 2016 5:43:57 PM
> To: Oracle-l Digest Users
> Subject: TTS Self-contained restriction workaround
>
> The requirements for TTS metadata export/import is that all tablespaces in a group should be self-contained.
>
> For example, if TS1 has a table that has a partition in TS9, then either move that table to TS1 or include TS9 in the group of tablespaces for metadata export.
>
> In our environment we have lots of tables that have their partitions spread across several tablespaces.
>
> We could include all those tablespaces in a group, but the problem is that as in example below, the TRANSPORT_TABLESPACES or TRANSPORT_DATAFILES do not allow PARALLEL degree to be set.
>
> And, we want to use PARALLEL just becuse these tablespaces have a lots and lots of Metadata. Without parallel it would just take several hours for the export/import.
> nohup impdp \"/ as sysdba\" parfile=migrate_tts.par > migrate_tts.log 2>&1 &
> ## migrate_tts.par
> DIRECTORY=MIG_DIR
> LOGFILE=MIG_TTS.log
> NETWORK_LINK=ttslink
> TRANSPORT_FULL_CHECK=no
> TRANSPORT_TABLESPACES=APP_DATA,APP_IDX,APP_DATA2
> TRANSPORT_DATAFILES='/oradata/APP/APP_DATA_01.dbf','/oradata/APP/APP_IDX_01.dbf',...
>
>
> -thanks
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l