Re: 7.0 rollback hassles

John,

For lack of any other info, I think we have to go by what Oracle says, which is:

        If a transaction needs to continue writing information from one
        extent to another extent in the rollback segment, ORACLE compares
        the current size of the rollback segment to the optimal size.  If
        the rollback segment is larger than its optimal size, and the extents
        immediately following the extent just filled are inactive, ORACLE
        deallocates consecutive non-active extents from the rollback segment
        until the total size of the rollback segment is equal to or is close
        to but not less than the optimal size.

They don't mention anything about bouncing the db, and since bouncing the db doesn't do anything (in your case at least), I think you should expect the behavior described above.

Regards,
Charles_Dye_at_corp.dialog.com

> From owner-oracle-l_at_CCVM.SUNYSB.EDU Tue Jan 16 11:19:15 1996
> Date: Tue, 16 Jan 1996 11:10:35 -0800
> From: John Baylis <jbaylis_at_CANFOR.CA>
> Subject: Re: 7.0 rollback hassles
> X-To: "ORACLE database mailing list." <ORACLE-L_at_CCVM.SUNYSB.EDU>
> To: Multiple recipients of list ORACLE-L <ORACLE-L_at_ccvm.sunysb.edu>
>
> I think I have a similar problem.
>
> Oracle 7.1 on NT.
> I have 4 rollback segments defined. minextents 14, maxextents 100.
>
> I recycled the oracle database (shutdown and restarted instance) and when I
> display v$rollstat it shows two rollback segments with number of extents =
> 100. The other two = 14 which is the minextents defined for each of the 4
> rollback segments that I have.
>
> Shouldn't all 4 segments have 14 extents when first starting up?
> Since maxextents = 100, 2 out of 4 segments cannot extend anymore?
> Am I missing something?
>
> Thanks for any insight!
Received on Tue Jan 16 1996 - 15:56:56 CST