Re: SMON and Coalesce of Free Extents

Hello Gene,

The current "wisdom" is to set PCTINCREASE to 0 on all tablespaces, and to use a fixed extent size policy for each tablespace, except SYSTEM. If you have access to MetaLink, search for the paper called "How to stop defragmenting and start living" for some more of the rationale. There is also a tip on my web site (1st URL below) on the matter of planning extents.

Regards,
Steve Adams

http://www.ixora.com.au/

http://www.oreilly.com/catalog/orinternals/

http://www.christianity.net.au/

On Tue, 01 Feb 2000 15:14:30 GMT, ghubert_at_skillspoint.com (Gene Hubert) wrote:

>In the days of Oracle 7.x I remember that auto-coalesce of free
>extents only happened if the pctincrease for a tablespace was
>non-zero. Does anyone know if this is still true? All I could find
>in the 8.0.5 docs was the following:
>
>---
>By default, SMON (system monitor) processes incrementally
>coalesce the free extents of tablespaces in the background. If
>desired, you can disable SMON coalescing.
>---
>
>I've always created tablespaces with pctincrease of 1 to enable
>coalescing but am wondering if this makes any difference now.
>
>
Received on Tue Feb 01 2000 - 19:09:05 CST