Re: Shrinking Rollback segments

Hi,

        This is an Oracle Bug. Referenece, i doesn't remember.

1. the rollback doesn't shrink back
2. when it does it corrupte the tablespace.

        example.

1. on tablespace of size 100000K + 1 Oracle block. pctincrease 0
2. 2 rolback into it. each of then initial 1000K next 1000K minextents 16 optimal 16000K maxextents 68.

                after a few time ( oracle in 7.1.[46]) doesn't coalesce the tablespace if the pctincrease of the tablespace is 0. You will see in the dba_free_space many free extents of 1000K, try to create an object of 1000K you will have an answer not enoughspace.

        So in 7.1.4 use static rollback segement

		initial 1000K next 1000K minextents 50 maxtents 50 optimal 50000K 
	like in oracle 6. that's work.

Francois.         

Ken Hensel <ken.hensel_at_nrl.navy.mil> wrote in article <338F1D95.3D0_at_nrl.navy.mil>...
> We recently upgraded to Oracle version 7.1.4 from 7.1.3. After doing
> this we noticed deleteing records caused the amount for free space in
> the tablespace containing the rollback segments as shown in
> sys.dba_free_sapce to go down. Even after commits, rollbacks and
> database restarts the space does not seem to be retrieved. After a
> while there is no longer any available space in the rollback segments.
> If anyone has heard of this before and can offer a hint as to how to
> work around this problem please let me know.
>
> Thanks
> Ken
>
  Received on Sat May 31 1997 - 00:00:00 CDT