Re: Change SYSTEM's default tablespace?

The wasted space comes from the MINEXTENT parameter. Everytime you create a segment (a table) as the SYSTEM user, it creates a segment with 50 extents. Personally, I think this is was a bad decision on the part of you previous DBA. You should not let objects in the database get to 50 extents to begin with. You should size objects properly from the beginning to fit into one extent to reduce fragmentation and increase performance. You can alter the tablespace's default storage to re-set MINEXTENTS to 1. Then, you can override the tablespace's default storage by putting storage clauses on your tables.

In article <39d12f90.84099247_at_news.mindspring.com>,   buckatl_at_yahoo.com wrote:
> I've been looking over some database creation scripts left by the
> previous DBA at my company and found the following:
> Early on in the db creation, the SYSTEM user is altered to set the
> default tablespace to USER1, which is obviously not an
> Oracle-generated tablespace. One of the attributes of this tablespace
> is minextents = 50 with extent size = 32k. When I use these scripts
> to create a database, I end up with huge amounts of apparently unused
> storage allocated to SYSTEM's tables in this tablespace. What would
> be the benefit of doing this?
> From my modest experience and knowledge I'm tempted to believe that
> perhaps the SYSTEM id should be left alone.
> Does anyone have any helpful thoughts on the topic?
> Thank you,
> Kenneth Buck
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Sep 26 2000 - 19:29:17 CDT