Re: Why pctincrease set to 1 for SYSTEM tablespace ?

There is one caveat to what Spencer said. If PCTINCREASE is set to zero in the DEFAULT STORAGE clause, free space will become fragmented BUT it may not be a concern. Take for example the rollback segment tablespace. If the rollback segments all have INITIAL and NEXT set to the same value (as they should except for a large rollback segment created for long running transactions and that should be in its own tablespace anyway), who cares if free space is fragmented? The fragments are the right size to be reused anyway.

Pete

spencer wrote:

> In short...
>
> for the TABLESPACE, specify
> DEFAULT STORAGE ( ... PCTINCREASE 1 ... )
>
> for TABLES, override the tablespace default, and specify
> STORAGE ( ... PCTINCREASE 0 ... )
>
> if PCTINCREASE is set to 0 in the DEFAULT STORAGE clause
> for the tablespace, then free space will become fragmented...
> and
> that means another set of tasks for an already overworked DBA...
>
> i say leave it set to 1 and let SMON manage the freespace
>
> "Matthieu Jobert" <mjobert_at_freesurf.fr> wrote in message
> news:946491895.203584_at_pepette...
> > In the script generated by Oracle 8.1.5 NT database creation
> assistant,
> > there is
> > REM ********** ALTER SYSTEM TABLESPACE *********
> > ALTER TABLESPACE SYSTEM
> > DEFAULT STORAGE ( INITIAL 100K NEXT 100K MINEXTENTS 1
> MAXEXTENTS 300
> > PCTINCREASE 1);
> >
> > Why is PCTINCREASE set to 1 and not to 0 ???
> >

Received on Thu Dec 30 1999 - 11:10:50 CST