Re: Oracle Import: Behaviour on Table Initial Extent

Hi,
Always try to set COMPRESS=N unless you want to defragment the Table and have plenty of Free Contigous Space in the Target Database where you are importing into.

Also , if you are creating an empty database then you might want to precreate those Big Tables with Smaller extent Sizes ,becuase it might not have space for the INITIAL,NEXT extent sizes of the Original Table.

-Thiru

Sybrand Bakker wrote:

> Hi Yat-Fan,
>
> Some clarification
> export can be done with compress=Y and compress=N
> The latter option will export all tables without modifications to the
> original storage clause.
> The former option will calculate the number of blocks allocated to the
> table, so basically the sum of all extents alllocated, and take that as
> value of initial in the storage clause. So with compress is yes the initial
> extent equals the size of the original table, whatever empty space there has
> been in that table.
> So you simply need to specify compress=n, or answer n to that question in
> interactive mode
>
> Hth,
> Sybrand Bakker, Oracle DBA
>
> Yat-Fan wrote in message <7kinl3$hio_at_ustsu10.ust.hk>...
> >Hi all,
> >
> >I found that the initial extent of an imported table is the final extent of
> >the original table, unless
> >the table skeleton is originally created.
> >
> >Here comes the problem when I have a large table with a large extent,
> >imported to a "empty" database since the each datafile is smaller than the
> >size of this extent.
> >
> >How can I ask the import/export facility to keep the original initial
> extent
> >of objects? (since I found that in the export dump file, the final extent
> is
> >taken as the initial).
> >
> >Many thanks.
> >
> >If possible, besides replying to the newsgroup, please cc: one copy of your
> >reply to me at fan.ho_at_alumni.ust.hk
> >
> >Rgds.,
> >fan (Yat-Fan Ho, KCRC, Hong Kong)
> >
> >
Received on Mon Jun 21 1999 - 12:14:54 CDT