Re: Q: Tablespace management

From: Bruno Jargot <see_at_reply.to.invalid>
Date: Thu, 10 Apr 2003 22:31:24 +0200
Message-ID: <htkb9v0aj61n582epid8lc4rf3ha3qlvl5@4ax.com>

On Thu, 10 Apr 2003 10:35:53 -0500, Vince Laurent wrote:

>I have a situation on one of our systems (Oracle 8.1.7.3).
>Seems there a few tables that have grown a bit. The NEXT
>extent for each of these tables is larger than the largest
>free chunk. Is there a way to adjust the NEXT on the fly
>(ie short of a reorg/imp/exp) to make the NEXT smaller?
>All the freespace chunks have been coalesed. My ultimate
>goal is to get these tables to thier own tablespaces but
>thanks to SAP they don't make it easy.

You should use tablespace with local management autoallocate. SAP recommends it and it will change your life.

You can change the next extent of a table with : alter table <nom_table> storage (next 64m); by example.

If you keep the dictionnary management, you should use only 3 or 4 size of extents :
64k, 4m, 64m by example (use power of two). It will reduce the fragmentation of the free space. Received on Thu Apr 10 2003 - 15:31:24 CDT