Doing export with compress = y is generally a BAD idea.
It results in an import file that defines a single extent
large enough to hold all your current extents. This
could make it hard to find a single file large enough
in the target tablespace, destroys your options for
a 'uniform extent' strategy, could waste a huge amount
of space (which you can, fortunately reclaim) and
is not needed to reduce performance-related fragmentation.
--
Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
James Belton wrote in message <8j9l2n$ghj$1_at_gxsn.com>...
>
> ... some reasonable advice and then ...
>
>Doing an export with compress=y is also a good idea. This reduces
>fragmentation, though you need to make sure that you have enough datafile
>space to take the size of the new initial extent.
>
Received on Tue Jun 27 2000 - 00:00:00 CDT
