Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Re:RE: Rollback Segments
Anita,
True on all counts with one caveat. Transactions is derived from sessions which is derived from processes. So in a practical world you need every public rollback segment you have, therefore they all come online immediately. In my case with processes = 300 that comes to 18 rollback segments. In reality we get along excellently on 10 private segments.
Like you I make use of private segments only. Makes for a lot easier troubleshooting and maintenance.
Dick Goulet
____________________Reply Separator____________________ Author: "A. Bardeen" <abardeen1_at_yahoo.com> Date: 5/9/2001 9:42 AM
Kevin,
This is a common misconception.
On startup Oracle determines the number of rollback
segments to bring on line based on the init.ora
parameters:
TRANSACTIONS / TRANSACTIONS_PER_ROLLBACK_SEGMENT
If the number of rollback segments specified by
ROLLBACK_SEGMENTS is less than that value, then Oracle
automatically will bring online any other PUBLIC
rollback segments to bring the total of online
rollback segments up to that value. Any PUBLIC
rollback segments remaining will be left offline.
PRIVATE rollback segments will only be brought online
automatically if specified in the ROLLBACK_SEGMENTS
parameter.
Misconception #2: TRANSACTIONS_PER_ROLLBACK_SEGMENT determines the number of concurrent transactions that can use a rollback segment. Granted that's what the name implies, but this isn't the case. This parameter is used only to determine the number of PUBLIC rollback segments to bring on line automatically at startup. The number of concurrent transactions that can use a rollback segment is based on many factors, the most important one being DB_BLOCK_SIZE.
I recommend using private rollback segments and specifying them in ROLLBACK_SEGMENTS because it makes it much easier to handle rollback segment problems. If there's a problem with a rollback segment on startup, for example, simply removing the segment from the init.ora will usually allow you to at least get the db open.
HTH,
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: A. Bardeen INET: abardeen1_at_yahoo.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: dgoulet_at_vicr.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Wed May 09 2001 - 13:09:45 CDT