Choosing a rollback segment

99% of our transactions are small; 1% are very large. Presently we have many large rollback segments: many because we have many small transactions, large because we have those few very large transactions. It would be nice if we could confine those large transactions to a few large rollback segments, and allow the rest of the rollback segments we need for the many small transactions to be small.

"set transaction use rollback segment", I hear you thinking. Yes, but what do we do if we want to be able to run multiple large transactions at once, and those transactions come from the same piece of code? How do we ensure that multiple large transactions don't use the same rollback segment? There's a dbms_something procedure with which one can set a rollback segment dynamically, but it isn't clear to me yet how we could decide which rollback segment to use on the fly. I may well be able to work something out with a little more research into the dba_ views, but would be interested to hear whether others have had this same problem and how they solved it.

Cheers,

--


| Dave Schweisguth                     CuraGen Corp., Bioinformatics Dept. |

| dcs_at_proton.chem.yale.edu             New Haven, Connecticut              |

| http://home.earthlink.net/~dschweisguth/         My opinions are my own. |

| For compliance with the NJ Right to Know Act: Contents partially unknown |