Re: Oracle 7.2: Need advice on Export/Import compression

In 7.3 ,if you want to get rid off the unused space use the following command:

    alter tabel table_name deallocate unused keep xk;

This command will deallocate the unused space keeping x kbytes only. The export/import utility is working the way it suppoesed to work. But, if you deallocate the space before the exporting, then the compress=N will result in the same number of extents in importing. On the other hand, compress=Y will result in compressing all of the data in one initial extent (65m in your case).

Mamdouh Khawaji
Certified DBA,
ARAMCO In article <6o1sii$vch$1_at_nnrp1.dejanews.com>,   paul.vincent_at_uce.ac.uk wrote:
> I have a table with an initial extent of 50Mb and 120 additional extents of
> 10Mb each. I know that a huge amount of the data has been deleted, so I need
> to compress it down (I estimate there's now about 65Mb of data there).
>
> According to the Oracle Server Utilities manual, exporting with COMPRESS=N
> would cause the subsequent re-import to recreate the table with an initial
> extent equal in size to the sum of all the current extents (i.e. 50Mb +
> 120*10Mb = 1250Mb). But it says if I run with COMPRESS=Y, then the initial
> extent of the recreated table should be only as big as necessary (i.e. I'd
> guess about 65Mb).
>
> However, when I run with COMPRESS=Y, then drop the table and re-import it,
> the table ends up with a 1250Mb initial extent, just as though I'd specified
> COMPRESS=N. Is this a known bug? Am I doing something wrong, or
> misinterpreting the manual? Any advice welcome!
>
> Paul
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Sat Jul 11 1998 - 10:35:57 CDT