hello,
At the same it would recommended that you move to locally managed tablespaces.
Amongst advantages:
o no fragmentation
o faster (no recursive sql to UET$ and FET$ to update the data dictionary)
o faster (try creating a dictionary managed table with 1000 extents, then do it with a LMT)
o faster (try dropping that table with 1000 extents now)
o faster (try a temporary tablespace in a DMT vs LMT -- benchmark it, its amazing)
About Rollback segments:
Place individual rollback segments into their own tablespaces.
You like to start with 15 or so rollback segments -- each with minextents=25 and maxextents=100. That would create 15 25meg rollback segments that can grow to 100meg each.
create tablespace RBS_01
datafile '/xxx/xxx/xxx/rbs_01.dbf'
size 25m reuse
autoextend on
maxsize 100m
extent management local uniform size 1m;
Then:
Create rollback segment rbs_01 tablespace rbs_01;
alter rollback segment rbs_01 online;
where:
o rollback segments are equi-sized extents.
o rollback segments are allocated large to avoid 1555's.
o rollback segments should be plentiful for the amount of transactions you do.
Hope this helps!
Best Regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
