Re: DIRECT=Y with EXP

On Thu, 1 Aug 2002 19:50:30 +1000, "Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote:

>
><Kenneth Koenraadt> wrote in message
>news:3d48fb68.668671_at_news.capgemini.se...
>> On Wed, 31 Jul 2002 20:16:29 +0200, Bruno Jargot
>> <see_at_reply.to.invalid> wrote:
>>
>> >On Wed, 31 Jul 2002 13:29:56 GMT, Kenneth Koenraadt wrote:
>> >
>> >>2) A direct mode exp/imp cannot be used for Data/tablespace
>> >>reorganisation. In worst case, an export file from a badly organised
>> >>database may cause the import database to *swell up*. Conventional
>> >>mode export prevents that.
>> >
>> >Could you, please, detail this assertion. I don't understand what you
>> >mean.
>>
>> Sure,
>>
>> Assume you have a table in the exp database with 30 rows and 100,000
>> blocks, this because most of the original 1,000,000 rows have been
>> deleted. That is certainly a waste of space. Importing this table
>> into another database with direct = Y will make the table just as
>> insufficient in the new database, as it imports the blocks directly. A
>> conventional mode exp/imp will just insert the 3 rows. Dot !
>>
>> - Kenneth Koenraadt
>
>
>I rather think you might be confusing direct=y with compress=y. The
>behaviour you describe is what compress=y will do. In and of itself,
>direct=y suffers no such problem.
>
>Regards
>HJR
>
>
>
>
>
>

Hi Howard,

I have tested on 9.2 and confirm that you are right (dang ;-)).

I thought that direct mode exp would export the raw blocks of a table, and that the import would just import these blocks, so a table with 3 rows and 100,000 blocks will be rebuilt that way in the import.

• Kenneth Koenraadt