Re: Paralelize CONSTRAINT VALIDATION during impdp
From: <noreply_at_maillard.im>
Date: Wed, 07 Aug 2013 22:10:01 +0200
Message-ID: <m01u65cleu.fsf_at_kcals.intra.maillard.im>
Mladen Gogala <gogala.mladen_at_gmail.com> writes:
Date: Wed, 07 Aug 2013 22:10:01 +0200
Message-ID: <m01u65cleu.fsf_at_kcals.intra.maillard.im>
Mladen Gogala <gogala.mladen_at_gmail.com> writes:
> On Mon, 05 Aug 2013 22:56:10 +0200, noreply wrote:
>
>> I do not have the exact numbers but what is sure is that the data
>> loading is just the quickest step and takes less than 1h30. The IMPDP
>> total time is more than 7 hours !
>>
>> Thank you for your suggestion.
>
> You can export constraints only like this:
>
>
> expdp userid=system schemas=SCOTT include=CONSTRAINT content=metadata_only dumpfile=constraints.dmp directory=TMP
[...snip...]
> and happily run the file thereafter. That's how it's done.
All of this suppose I am doing a 2-step impdp job, right ?
First schemas objects without constraints and then, only constraints but using the novalidate "universal hammer". Is that right ?
Thank you.
-- XMAReceived on Wed Aug 07 2013 - 22:10:01 CEST