In our warehouse, we had a RBS tablespace of 25Gig. After conversion to
Undo, the Undo Tablespace was reduced to 6 Gig - and I personally think it
could be much smaller.
One suggestion that might work for you is to initially create the undo
tablespace the same size as the RBS tablespace with autoextend turned on so
that it could grow if it needs to. You could then monitor it and shrink the
size of the file when you see (via HWM) how much space is actually being
used.
I have been pleasantly surprised - it is much more efficient than using RBS.
Good Luck!
Tom Mercadante
Oracle Certified Professional
-- --Original Message-- --
From: Paula_Stankus@(protected) [mailto:Paula_Stankus@(protected)]
Sent: Tuesday, May 18, 2004 4:34 PM
To: oracle-l@(protected)
Subject: RE: undo segments vs. rbs
I am working on moving a productional database from 8.0.6 to 9i. I have = a
question: if I have 10 rbs at 128K (initial and next extent) and one =
"large " on at 10,485,760 bytes how does that translate into undo = segments?
=20
Are there any best practices on sizing undo segments?
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
