Re: Should I use public rollback segments?

My understanding of this is that public rollback segments only really come into play with OPS environments. If your not using OPS its a moot point since only one instance can connect to a database and thus only instance will use the rollback segments regardless of whether or not they are public or private. As far as corruption goes, you're in a bad situation if your rollback segments get corrupted regardless of whether or not they are public or private. The database is not going to allow you to open the db if there are pending transactions in a corrupt rollback segment; you must recover the rollback segment first. If you are using OPS, my personal bias is towards private rollback segments because it gives the DBA more control over what instance get what rollback segment. The DBCA should have an option to create scripts instead of actually creating the instance. Use this option and edit the part of the script that creates the rollback segments or let the DBCA create the database and then go in and drop / recreate the rollback segements by hand.

"Calvin Crumrine" <Calvin_Crumrine_at_dced.state.ak.us> wrote in message news:3C1FA1C8.CDF67432_at_dced.state.ak.us...

> Setting up an 8i database. I noticed that the DBCA creates public
> rollback segments. IIRC I was told that public segments aren't a good
> idea. I believe the reasoning was that since they're brought online
> automagically if one gets corrupted you can't start the instance. Won't
> swear that that's the reason because I'm still trying to find the note I
> made, but whether I have the right reason or not can you confirm whether
> I should be using them or should I tell DBCA to create private segments
> & if so, how?
>
> thanks.

-- 
Posted from d225s244.hotbank.com [63.83.225.244] 
via Mailgate.ORG Server - http://www.Mailgate.ORG