Re: Rollback Segment Trouble

From article <shatzmanCq0nDD.83q_at_netcom.com>, by shatzman_at_netcom.com (bs):
>
> : to fix the problem 1) increase the PCTINCREASE value in storage clause of
> : the rollback tablespace or 2) set a higher INITIAL value in the storage
> : clause of the rollback tablespace. The latter will require you to drop the
> : table space and recreate it. The PCTINCREASE change will take effect the
> : next time a transaction is run. Warning: there is a point where larger
> : extents will hurt performance so don't carried away with your INITIAL
> : value.
>
.
.
> Barry

        With this talk about maxextents I was woundering if someone could tell me how to find out how many extents are currently being used for a normal data/index tablespace.
Ive just had a prob with exceding the max no of extents on a tablespace  (ie >121 extents ). but I would like to be proactive about this so it wont happen again.
Ive been looking at dba_extents for that tablespace but I couldnt see where 121 figured into it.

So could someone please send me a script to do this or a direction of where I should be looking.

Thanks,

        John.

-- 
John Zentveld                          Internet: jzentvel_at_scu.edu.au
Southern Cross University              Phone (066) 20 3219
Lismore NSW Australia