Re: Importing a compressed table doesn't go to smallest suitable free space

What you do is to create the table before running your import. You define what the table space parameters are, then run the import. "Compress" in dealing with IMP/EXP means to put into one extent, not compress as in reduce in size. If you want to reduce it, you create the table specifying a smaller initial extent.

In article <4g8d1o$6b1_at_madison.tdsnet.com>, Ken Friday <ken.friday_at_teldta.com> says:
>
>chicnorm_at_norm.inforamp.net (Norm LeBlanc) wrote:
>>I am trying to import a table that I had previously exported with the
>>compress extents option and I am expecting it to be placed in the
>>smallest available contiguous block of free space that it will fit in.
>>But this does not happen. Am I expecting too much?
>>
>>Dinesh Fernandopulle
>>
>>
>My understanding of "compress extents" is that the initial extent storage
>parameter is set equal to the sum of existing extents allocated. It does
>not adjust for actual data volumes.
>
>Ken F.
>
>--
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
  Received on Fri Feb 23 1996 - 00:00:00 CET