Originally posted by anujpathak Bigest insert update delete on a table before commit won't be more then yr bigest table in the database if it is so u may keep bigest rollback segmenet equal to the bigest table size of yr database
make it online before yr process
use set transaction use rollbacksegment statment before process
make it ofline once u finished yr process
I do it this way it may help you too.
You have to do a commit before to use the set transaction use rollback segment rbs_big statement.
If you make it offline once you are finished ONLY, other transactions will share the large rollback segment. If you don't want to share it take it OFFLINE as soon as you assign the transaction to the segment. As I said, NO other transactions will be able to access it whilst the rollback's segment is in OFFLINE-PENDING state.
And remember, an explicit commit will end the current transactions assignement to the SET TRASACTION TO ROLLBACK SEGMENT.
*Oh, my 500th post, well, time to take a tiny bow. Slow and steady they say.*