My experience shows that, if you don't COALESCE by rebuilding,
export/import or tablespace( pctincrease =1), when there are lot of
deletes/inserts, the space never gets released to the system.
It keeps on adding new extents even though there may be, tons of
UN-COALESECED free space in the old extents.
Raoul De Kezel <100653.2230_at_compuserve.com> wrote in article
<MPG.fc54069a33c27919896b3_at_news.compuserve.com>...
> In article <01bd7ec6$736eaf60$a504fa80_at_mndnet>, suresh.bhat_at_mitchell-
> energy.com says...
>
> Thank you for your answer. I'll try to find the discussion in dejanews.
>
> > One suggestion:
> >
> > As you have planned use pctincrease = 0 for tables. USE PCTINCREASE =1
for
> > TABLESPACES. If you do this Oracle SMON process will automatically
> > defragment the space after deletions/inserts etc.
>
> I'm afraid I'll ask another FAQ: I used PCTINCREASE = 0 for tablespaces
> on purpose to disable SMON's coalescing. In the configuration I
> described, all the (allocated) extents in a given tablespace will have
> the same size. I don't see the point to merge them just to break the
> result again later. I hope to save some I/O that way.
>
> Am I missing something ?
>
> --- Raoul
>
>
Received on Mon May 18 1998 - 16:33:19 CDT
