Re: CURSORS AND ROLLBACK SEGMENTS

It is not as simple as that.

Rollbacks are used for read consitancy. The fact that you commit does not recude the need for RBS as other transactions may need the data from before your commit.

In your case you sould not only do a commit but also close the cursor, reopen and reposition on the last trated record+1.

30,000 rows is not mutch, I would increase rollback space and not bother with intermediate commits. (6GB of diskspace installed is about the same cost as a day of programming).

Good luck,

Johnny Verhoeven

jgopinath_at_gt.com wrote:
>
> Hi, I have a CURSOR which selects around 30,000 rows. I then process the rows
> returned by the CURSOR. After processing each row, I do a commit. THe stored
> procedure seems to process around 10,000 rows and then throws up an error
> saying that the rollback segment is too small. No other errors are generated
> by the procedure. My understanding was that if we do a commit after each row
> is processed, there is no reason for the rollback segment to be filled. Am I
> missing something here?? ANy help would be appreciated. Thank You, rgds
> Jayadev
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Fri Apr 02 1999 - 15:20:48 CST