Re: Rollback segment doesn't shrink back to optimal

Rollback segments only shrink automatically when a NEW transaction causes the head pointer to cross an extent boundary. In other words, you won't necessarily see shrinkage even if you were to start another transaction straight after your first one... that new transaction will have to acquire enough rollback blocks to cause it to cross into a new extent before the shrink happens.

All of which is beside the point anyway: you don't *want* automatic shrinkage, not if you value performance. Issue the 'alter rollback segment blah shrink to 500M' (or whatever size is appropriate), and the thing will shrink to whatever size you want at a time and a place of your choosing.

Incidentally, God knows why your RBS tablespace has a pctincrease of 50. Your segments, you say, have a pctincrease of 0 -and that's exactly as it should be. So why have it wrong at the tablespace level?

And finally: Unless you are using Oracle 6, you certainly don't need 20 extents. You can manage quite happily with 5 or 6 extents these days.

Regards
HJR

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------

<fsiegel_at_my-deja.com> wrote in message news:8s7a88$ofr$1_at_nnrp1.deja.com...


> The transaction is committed!!  And no other transactions are using this

> rollback segment.   And I even disconnected from the client.

>

>

> > rollback segment will not shrink back to optimal size after a

> transaction ends

>

>

> Sent via Deja.com http://www.deja.com/

> Before you buy.