I don't think it does, Paula. Since you don't have control over the = number and sizes of your undo segments, there really isn't a direct = correlation. Sizing undo really comes down to two questions: 1.) How long is your longest running query? Make sure your undo_retention is at least that large. 2.) How much undo will your database generate in the amount of time specified in undo_retention? Make sure your undo tablespace is at least that large. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Paula_Stankus@xxxxxxxxxxxxxxx Sent: Tuesday, May 18, 2004 4:34 PM To: oracle-l@xxxxxxxxxxxxx Subject: RE: undo segments vs. rbs I am working on moving a productional database from 8.0.6 to 9i. I have = =3D a question: if I have 10 rbs at 128K (initial and next extent) and one = =3D "large" on at 10,485,760 bytes how does that translate into undo =3D segments? =3D20 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@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //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@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------