Re: Database Size?

Nick <nick_j_at_mailcity.com> writes:

> We have very large roll-back segments setup - I dont know how Oracle treats
> Rollback, but we have the segments R01, R02, R03 etc and SYSTEM - The R*

Why so huge? Have one big one for batch loads and only use it for batch loads eg-

alter rollback segment big online;
set transaction use rollback segment big; <batch processing>
alter rollback segment big offline;

But 1 gig is almost certainly overkill. (If you were running into rollback problems trying to load the data and you created 1 gig rollback segments to handle the load, a better way would have been to increase the frequency of commmits during the load.)

The rest of the rollback segments should be sized appropriately for your ongoing transactions. My first response applies:

> > at fault, not the least of which is that you could create a
> > tablespace with hundreds of Gig. of allocated space in it,
> > and not have any data at all. Oracle isolates physical

The rollback segments must reside in a tablespace which is composed of pre-allocated disk files. Try checking out the Concepts Manual in the generic documentation. It explains the concepts of rollback segments, tablespaces, and disk allocation pretty well.

--Maury Received on Mon Oct 25 1999 - 06:55:57 CDT