Re: DIRECT=Y with EXP

<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 Received on Thu Aug 01 2002 - 04:50:30 CDT