-
make the tablespace bigger, also your next extent seems to be 1.9gb is that correct
-
if your next extent is 1.9gb then even you have 16gb free space in your tablespace but if none of extents has 1.9gb contiguos free space you will see this problem.
1.9gb next extent is way too big IMHO, you can either change next extent to a smaller value or increase your tablespace size but doing so might waste your existing free space
-
I'm with Pando here.
Big extents make big messes. Smaller, uniformly sized extents will perform well and actually make management easier.
We generally use 1M, 10M and 100M extents.
-
KenEwald
just for my knowledge
u said We generally use 1M, 10M and 100M extents
what storage value u assign for pctincrease.minextents,maxextents parameters?
-
0 pctincrease, 1 min, max depends on whether we want to cap growth or autoextend.
-
ken
Thanks for the answer
just one question -
is there any rule of thumb for pctincrease value.
i mean any percentage ?
-
I'm not Ken, but pctincrease should always be 0 in Dictionary Managed Tablespaces. It is ignored (except at segment creation if minextents > 1) in Locally Managed Tablespaces.
John
-
Originally Posted by gajananpkini
ken
Thanks for the answer
just one question -
is there any rule of thumb for pctincrease value.
i mean any percentage ?
yes ZERO
-
pando boss Thank u very much for the answer.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|