Re: rollback segment

It seems to me that you can get by with just 36 MB in one tablespace:

	4 rollback segments:
		1MB initial
		1MB next
		minimum extents 2
		optimal 2MB
	This would max out as follows:
		3 segments @2MB (optimal)	 6 MB
		1 segment @30MB (large job)     30 MB

By using optimal in this way, you don't care which segment your large job uses. It will expand as needed (28 space management events should not be noticable) and shrink back to 2MB when the job is over.

Nancy Teh wrote:
>
> Hello,
>
> I have a problem here with rollback segment.
>
> I have a big tansaction which run once a month that required a big
> rollback segment of 30M. My normal production online application only
> required 4 rollback segments of total size of 16M in the RBS tablespace.
>
> I have created a separate RBS2 tablespace of 40M to accomodate this
> monthly transaction. so at present I have 2 tablespaces for rollback
> segemnts and used up 56M in total of disk space.
>
> Can anyone suggest a better way of dealing with this problem? Should I
> create one RBS tablespace of 40M and put both the production and the big
> rollback segments in it.
>
> Any suggestions would be appreciated. You can send an email to
> nancy.teh_at_cc.monash.edu.au
>
> Thank in advance...:)
>
> Regards,
> Nancy
> ____________________________________________________________________
> Nancy Teh
> Shared Systems, Computer Centre,
> Monash University, Wellington Road,
> Clayton, Victoria 3168
> Australia
> Email:Nancy.Teh_at_cc.monash.edu.au
> ______________________________________________________________________
Received on Wed Apr 22 1998 - 21:22:51 CDT