Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Understanding Rollback Segment Sizes
Hi All,
I have what I think is probably a very basic question. I'm having a bit of a problem understanding how to size my rollback segments, if I have reserved too much or too little space, and whether I have enough of them.
I am setting up a new Oracle 9.2.0 database and our company has four SQLs for creating the databases - one SQL each for sizing based on small, medium, large, and extra-large databases. I am not too familiar with all the items in there and I want to understand what it is doing instead of just blindly trusting what someone else set up years ago for an Oracle 8i system...things change but these scripts may not have.
So here is where I stand:
- I am on an AIX 5L system
The database creation SQL indicates I should make four (4) data files for the RBS (3 X 1GB, 1X 500MB).
alter tablespace esindl01rbs
add datafile '/oradata01/l01/rbs/esindl01rbs03'
size 1000M autoextend OFF;
alter tablespace esindl01rbs
add datafile '/oradata01/l01/rbs/esindl01rbs04'
size 1000M autoextend OFF;
I should then create four rollback segments that each appear exactly the same as below:
create rollback segment esindl01_rbs01 tablespace esindl01rbs storage(initial 50M next 50M minextents 2 maxextents 10 optimal 300M);
So my questions here are:
I checked the V$ROLLSTAT and there are almost now extends or shrinks, and a book I am reviewing on tuning indicates all four are 99.9% hitting the mark (waits vs gets). As I said, I'm not really trying to tune this database, but rather understand why something is set a certain way and whether I am actually wasting space, which I think I am.
Thanks in advance.
Steve Received on Wed Jan 17 2007 - 17:00:01 CST
![]() |
![]() |