Re: [EXT] impdp (no TTS) and deferred segment creation

From: Andy Klock <andy_at_oracledepot.com>
Date: Fri, 28 Feb 2014 13:52:14 -0500
Message-ID: <CADo_RaOG2kbX-ONHBy0JdskZmY6-Swv5m6aJ-LM81HHOBLD+Yw_at_mail.gmail.com>

On Fri, Feb 28, 2014 at 12:52 PM, "Uwe Küchler" <uwe_at_kuechler.org> wrote:

>
> I think you misunderstood me. If I do NOT provide any transformation
> arguments, then the correct segment creation clause should be in the
> SQLFILE. But there is no such clause. IMHO, if the import does create
> segments immediately, there should as well be a "segment creation
> immediate" clause in the sqlfile. But there isn't.
>
>

Ah, probably misunderstanding. I do that. It actually should, I agree, but you exported from an Standard Edition database which doesn't support deferred segment creation, so that is probably why it is missing.

There is some weird language in the doc that is slightly ambiguous:

"SEGMENT_CREATION - If set to y (the default), then this transform causes the SQL SEGMENT CREATION clause to be added to the CREATE TABLE statement. That is, the CREATE TABLE statement will explicitly say either SEGMENT CREATION DEFERRED or SEGMENT CREATION IMMEDIATE. If the value is n, then the  SEGMENT CREATION clause is omitted from the CREATE TABLE statement. Set this parameter to n to use the default segment creation attributes for the table(s) being loaded. (This functionality is available starting with Oracle Database 11g release 2 (11.2.0.2).)"

Meaning, you can't change a "SEGMENT CREATION IMMEDIATE" to be"SEGMENT CREATION DEFERRED" with this parameter since it is getting this from the source. However, using TRANSFORM=SEGMENT_CREATION:n will cause it to be omitted completely from the import and then you may get some mileage from your deferred_segment_creation=TRUE setting.

Have a good weekend too!

Andy K

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

Received on Fri Feb 28 2014 - 19:52:14 CET