Re: extent allocation?

In article <1992Oct31.103337.1_at_us.oracle.com>, sstephen_at_us.oracle.com writes:
> In article <1992Oct28.165739.20340_at_gdstech.grumman.com>,
 un_at_gdstech.grumman.com (Un Fu) writes:
> > When Oracle requests an extent of block size 210, does it
.
.
stuff deleted
.
> Recently, I had a job of importing a 250 Meg database on a monthly basis. Of
> course, I would get ORA-1547 every time I ran it, but this was because I had a
> large table being imported in after a small table had split the tablespace. To
> get around this, I had to "de-fragment" my tablespace into 1 large extent
> again, before I started importing. To do this, (assuming that my tablespace
> was one datafile, exactly 250000 blocks.
>
> CREATE TABLE BIG_TEMP STORAGE (INITIAL 250000 MINEXTENT 1);
> -- table created
> DROP TABLE BIG_TEMP;
>
> et voile, my tablespace's extents were re-combined into one big extent, and
> my import would always succeed.

There is a utility called 'fsc' (Free Space Compress) which compresses free space in a datafile. This utility was written by Oracle UK. I think the division is called the 'Performance Studies Group'. It is an unsupported software but very usefull. It does not shift objects within a datafile. All it does is to compress contiguous free space. Speak to your Oracle account manager if you want a copy.

-- 
 _____       ________ / ____ |Tony Jambu, Database Administrator
  /_  __       /_ __ /       |Colonial Mutual Life Australia. (ACN 004021809)
 /(_)/ ((_/ \_/(///(/_)/_(   |EMAIL:  TJambu_at_cmutual.com.au
 \_______/                   |PHONE:  +61-3-6076448       FAX:  +61-3-6076198