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

Use IGNORE=Y when you import the data back. In that case, you can create the tablespace and use the correct value for initial extent and next extent. And Oracle import the data in IGNORE=Y mode, oracle will not recreate the tablespace and change the values for you. In that case, you will have a "new" table with correct parameter.

Winnie Liu
poohland_at_hotmail.com

paul.vincent_at_uce.ac.uk wrote in message <6o1sii$vch$1_at_nnrp1.dejanews.com>...
>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
Received on Thu Jul 09 1998 - 21:30:08 CDT