Re: Export - Compress question

However, you didn't recreate the table, if I read correctly. So your initial extent is not 400k, as it should have been after import of a file with compress extents.
So it is not amazing the table is not in one single extent.

Regards,

Sybrand Bakker, Oracle DBA

Van Messner <vmessnerNOvmSPAM_at_discovernet.com.invalid> wrote in message news:06dd4dce.6e4530e7_at_usw-ex0106-047.remarq.com...
> I have a table of 400K bytes with an inital extent of 256K and
> a next of 4K. It has thrown extents.
> I exported the table, truncated the table, reset the storage
> parameter next to 256K and imported the table. The export
> parfile had compress=Y.
> After import the table came back in at two extents. I thought
> compress always forced the existing rows into one extent.
> Did I miss something?
>
> Van
>
> PS: the only table index which was 350K had an initial extent
> of 256K and a next of 4K. I reset its storage parameter next to
> 256K when I did the table. After import the index is in one
> extent.
>
> * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network
*
> The fastest and easiest way to search and participate in Usenet - Free!
>
Received on Fri Mar 24 2000 - 11:54:17 CST