Re: rollback segment reached maximum extent

You certainly don't need to shut down the db to fix this problem. But, when you offline a rollback segment you have to wait until pending transaction are completed. You are really doing an "offline pending" and it could take a while to finish the pending stuff. So, Sally's technique of adding the new ones first is a good one. The get used immediately. You can also edit them into the init.ora file and comment out the old ones so that next time you take a bounce the old ones are offline for sure and you can drop them easily. Otherwise, add the new ones (configured all nice and tidy, of course) and offline the old ones and wait a while. When they are really offline, drop them.

Roger

Sally Pearce wrote:
>
> When we had this problem we took the rollback segments offline (one at a
> time), dropped them, then recreated them with the new storage parameters.
> It worked fine - we have 10 rollback segments so the users didn't miss the
> offline one. You could create a new segment with the desired storage
> parameters, bring it on line, then drop the others one at a time, since you
> only have 4. If this will blow your tablespace you can add another
> datafile, assuming you have the disk space.
>
> kgsudhi_at_my-dejanews.com wrote in article <7hr901$t3f$1_at_nnrp1.deja.com>...
> > Thank You Rich.
> > This is a 24x7 LIMS System. An Export/Import may need a 6-8 Hrs
> > downtime. Is there any other method so that I can compress the extents
> > to one? Can I change the table's storage parameters with out dropping
> > it?
> >
Received on Sat May 22 1999 - 09:55:31 CDT