Re: ROLLBACK SEGMENTS: Some basic questions

Hi Arif,

   The best solution is commit after every 100 transactions;     

amar

Atif Ahmad Khan <aak2_at_Ra.MsState.Edu> wrote in article <aak2.853630433_at_Isis.MsState.Edu>...
>
> 1. Is there a way to have a transaction not use any rollback segment ?
>
> I am more concerned about performance and data loss is not really a
> concern.
>
> 2. I have a rather complicated PL/SQL script that works on a table that
> has 140,000 rows in it. The script is deleting rows based on a set of
 rules.
> The process after 30 minutes aborts and reports the following :
>
> BEGIN
> *
> ERROR at line 1:
> ORA-01562: failed to extend rollback segment number 1
> ORA-01628: max # extents (100) reached for rollback segment R01
>
> I thought I had taken care of all my rollback segment blues when I
 created
> the following rollback segment :
>
> create public rollback segment r01 tablespace RBS
> storage (initial 500K NEXT 500K OPTIMAL 10M MINEXTENTS 15 MAXEXTENTS 100)
 ;
>
> I dropped all the other rollback segments intentionally to help me debug
> this problem. I am now thinking that maybe I should increase the
 maxextents
> to 200 or some such number and maybe add another rollback segment with
> identical settings. But I am not sure if that is going to solve my
 problem.
>
> Any ideas ?
>
> Atif Khan
> aak2_at_ra.msstate.edu
>
  Received on Sat Jan 25 1997 - 00:00:00 CST