Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: best parameters for tablepsace
On 1 May 1997 13:01:33 GMT, <uday.v.lad_at_att.com> wrote:
> pctincrease 1 is batter as SMON colasce tablespace when it is fragmented.
>keep max extents unlimited but max size should be controlled by the limit
>of your hard disk device.
>other wise seems ok.
>
>Bob Yeh <tyeh_at_csc.com> wrote in article <33676313.5DD1_at_csc.com>...
>> Most people I have seen set the tablespace pctincrease to 0, 1 or
>> 50(default) or 100. They all have their own pros and cons.
>>
>> With the new features of 7.3, I want to set
>> autoextend on,
>> maxsize unlimited,
>> maxextents unlimited,
>> pceincrease 1.
>>
>> Is this a good choice? What are the things need to watch out for?
Some people advocate the fixed extent size per tablespace policy. This means you put (initial X next X pctincrease 0) in the default storage clause of the tablespace, and never specify those things for individual segments. Some tablespaces are set up to have small extents and others are set up to have bigger ones, then segments are assigned to tablespaces as appropriate. This avoid fragmentation entirely, so coalescing is undesireable.
Steve Adams Received on Fri May 02 1997 - 00:00:00 CDT
![]() |
![]() |