Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Rollback Segs

RE: Rollback Segs

From: Lee Cullip <Lee.Cullip_at_three.co.uk>
Date: Wed, 16 Jul 2003 13:02:19 +0100
Message-Id: <25937.337999@fatcity.com>


This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------_=_NextPart_001_01C34B92.1B7385D0
Content-Type: text/plain;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I think that's probably the case with most third party applications, if developers haven't coded their apps to use a large rollback segment for certain transactions (which I find is the case with most developers ;-) = )
then the only option is to turn off all but the large rollback seg.
=20

Cheers
Lee
=20

-----Original Message-----
From: Fermin Bernaus [mailto:fbernaus_at_sammic.com] Sent: 16 July 2003 11:19
To: Multiple recipients of list ORACLE-L Subject: RE: Rollback Segs

=20

    Yes you are right, sorry but I made a mistake, since we are using = Baan
IVc4 which works against Oracle we have no means to interfere with its transactions when they are commited to Oracle and we can not modify = them so
that it uses a specific rollback segment, so the only way for us to do = it is
to disable all except the one we want it to use.

-----Mensaje original-----
De: Lee Cullip [mailto:Lee.Cullip_at_three.co.uk] Enviado el: mi=E9rcoles, 16 de julio de 2003 10:54 Para: Multiple recipients of list ORACLE-L Asunto: RE: Rollback Segs

set transaction use rollback segment xxxx only works if it's the first statement in your transaction, an easy way to make sure this is the = case is
to issue a commit directly before issuing this statement. I believe this has been a feature of Oracle since way back in version 7 (Correct me if I'm wrong).
=20

Hope this helps.
Cheers
Lee

-----Original Message-----
From: Fermin Bernaus [mailto:fbernaus_at_sammic.com] Sent: 16 July 2003 09:09
To: Multiple recipients of list ORACLE-L Subject: RE: Rollback Segs

=20

    Which database version are you using? as long as I know, at least = on
Oracle 8.0.6 you can not specify which rollback segment a particular transaction should use. We disable all rollback segments and only = enable
those which we know won't make big updates / deletes crash.
=20

-----Mensaje original-----
De: venkat Rama [mailto:techsqlca_at_yahoo.com] Enviado el: mi=E9rcoles, 16 de julio de 2003 6:34 Para: Multiple recipients of list ORACLE-L Asunto: Rollback Segs

Hi Friends,
=20

I have 150Gb database with 30 rollback segs with optimal settings!! for normal operations no problems!! But we are doing massive updates for = some of
big tables!! So we are using vb programs and connecting to the database = thru
odbc dsn. My first question is how to set transaction use rollback = segment
rbs_big? I tried to set as first stmt, but its not using rbs_big = segment,
its using some other rollback segment. Is that good idea to make all my rollback segs maxextents unlimited to avoid maxextents reached error?? = I
have lot of rbs space nearly 10Gb. I saw one time, one of my rbs = segment
extented 2gb and failed transaction with maxextents reached with 5m = initial
and next, minextents 20 and optimal 100M.
=20

Any help will be appreciated
Thanks
venkat.
=20
=20
=20
=20

  _____ =20

Do you Yahoo!?
SBC
<http://pa.yahoo.com/*http://rd.yahoo.com/evt=3D1207/*http://promo.yahoo= .com/s
bc/> Yahoo! DSL - Now only $29.95 per month!

________________________________________________________________________=


This e-mail message (including any attachment) is intended only for the personal=20
use of the recipient(s) named above. This message is confidential and = may be

legally privileged. If you are not an intended recipient, you may not review, copy or=20
distribute this message. If you have received this communication in = error,
please notify=20
us immediately by e-mail and delete the original message.

Any views or opinions expressed in this message are those of the author only.=20
Furthermore, this message (including any attachment) does not create = any
legally=20
binding rights or obligations whatsoever, which may only be created by = the
exchange=20
of hard copy documents signed by a duly authorised representative of Hutchison=20
3G UK Limited.

________________________________________________________________________=




------_=_NextPart_001_01C34B92.1B7385D0
Content-Type: text/html;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D091280112-16072003><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
think that's probably the case with most third party applications, if = developers=20
haven't coded their apps to use a large rollback segment for certain=20 transactions (which I find is the case with most developers ;-) ) then = the only=20
option is to turn off all but the large rollback = seg.</FONT></SPAN></DIV>
<DIV><SPAN class=3D091280112-16072003><FONT face=3DArial = color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D091280112-16072003><FONT face=3DArial = color=3D#0000ff=20
size=3D2>Cheers</FONT></SPAN></DIV>
<DIV><SPAN class=3D091280112-16072003><FONT face=3DArial = color=3D#0000ff=20
size=3D2>Lee</FONT></SPAN></DIV>
<DIV><SPAN class=3D091280112-16072003><FONT face=3DArial = color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">   <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Fermin Bernaus=20   [mailto:fbernaus_at_sammic.com]<BR><B>Sent:</B> 16 July 2003 = 11:19<BR><B>To:</B>=20
  Multiple recipients of list ORACLE-L<BR><B>Subject:</B> RE: Rollback=20   Segs<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>   <DIV>&nbsp;&nbsp;&nbsp;&nbsp;<SPAN class=3D766261509-16072003><FONT = face=3DArial=20
  color=3D#0000ff size=3D2>Yes you are right, sorry but I made a = mistake, since we=20
  are using Baan IVc4 which works against Oracle we have no means to = interfere=20
  with its transactions when they are commited to Oracle and we can not = modify=20
  them so that it uses a specific rollback segment, so the only way for = us to do=20
  it is to disable all except the one we want it to = use.</FONT></SPAN></DIV>
  <BLOCKQUOTE>
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20

    size=3D2>-----Mensaje original-----<BR><B>De:</B> Lee Cullip=20     [mailto:Lee.Cullip_at_three.co.uk]<BR><B>Enviado el:</B> mi=E9rcoles, = 16 de julio=20

    de 2003 10:54<BR><B>Para:</B> Multiple recipients of list=20     ORACLE-L<BR><B>Asunto:</B> RE: Rollback Segs<BR><BR></FONT></DIV>     <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff=20

    size=3D2>set transaction use rollback segment xxxx only works if = it's the=20

    first statement in your transaction, an easy way to make sure this = is the=20

    case is to issue a commit directly before issuing this=20     statement.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff size=3D2>I=20

    believe this has been a feature of Oracle since way back in version = 7=20

    (Correct me if I'm wrong).</FONT></SPAN></DIV>     <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff=20

    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff=20

    size=3D2>Hope this helps.</FONT></SPAN></DIV>     <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff=20

    size=3D2>Cheers</FONT></SPAN></DIV>
    <DIV><SPAN class=3D939005207-16072003><FONT face=3DArial = color=3D#0000ff=20

    size=3D2>Lee</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">       <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20

      size=3D2>-----Original Message-----<BR><B>From:</B> Fermin = Bernaus=20

      [mailto:fbernaus_at_sammic.com]<BR><B>Sent:</B> 16 July 2003=20
      09:09<BR><B>To:</B> Multiple recipients of list=20
      ORACLE-L<BR><B>Subject:</B> RE: Rollback =
Segs<BR><BR></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
      <DIV>&nbsp;&nbsp;&nbsp;&nbsp;<SPAN class=3D277150407-16072003><FON=
T=20
      face=3DArial color=3D#0000ff size=3D2>Which database version are =
you using? as=20
      long as I know, at least on Oracle 8.0.6 you can not specify =
which=20
      rollback segment a particular transaction should use. We disable =
all=20
      rollback segments and only enable those which we know won't make =
big=20
      updates / deletes crash.</FONT></SPAN></DIV>
      <DIV><SPAN class=3D277150407-16072003><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <BLOCKQUOTE>
        <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
        size=3D2>-----Mensaje original-----<BR><B>De:</B> venkat Rama=20
        [mailto:techsqlca_at_yahoo.com]<BR><B>Enviado el:</B> mi=E9rcoles, =
16 de=20
        julio de 2003 6:34<BR><B>Para:</B> Multiple recipients of list=20
        ORACLE-L<BR><B>Asunto:</B> Rollback Segs<BR><BR></FONT></DIV>
        <DIV>Hi Friends,</DIV>
        <DIV>&nbsp;</DIV>
        <DIV>
        <DIV><FONT face=3DArial size=3D2>I have 150Gb database with 30 =
rollback segs=20
        with optimal settings!! for normal operations no problems!! But =
we are=20
        doing massive updates for some of&nbsp;big tables!! So we are =
using vb=20
        programs and connecting to the database thru odbc dsn. My first =
question=20
        is how to set transaction use rollback segment rbs_big? I tried =
to set=20
        as first stmt, but its not using rbs_big segment, its using =
some other=20
        rollback segment. Is that good idea to make all my rollback =
segs=20
        maxextents unlimited to avoid maxextents reached error?? I have =
lot of=20
        rbs space nearly 10Gb. I saw one time, one of my rbs segment =
extented=20
        2gb and failed transaction with maxextents reached with 5m =
initial and=20
        next, minextents 20 and optimal 100M.</FONT></DIV>
        <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2>Any help will be =
appreciated</FONT></DIV>
        <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
        <DIV><FONT face=3DArial size=3D2>venkat.</FONT></DIV></DIV>
        <DIV>&nbsp;</DIV>
        <DIV>&nbsp;</DIV>
        <DIV>&nbsp;</DIV>
        <DIV>&nbsp;</DIV>
        <P>
        <HR SIZE=3D1>
        Do you Yahoo!?<BR><A=20
        =

href=3D"http://pa.yahoo.com/*http://rd.yahoo.com/evt=3D1207/*http://prom= o.yahoo.com/sbc/">SBC=20

        Yahoo! DSL</A> - Now only $29.95 per=20     month!</BLOCKQUOTE></BLOCKQUOTE><CODE><FONT=20     =

size=3D3><BR><BR>_______________________________________________________=
_________________<BR><BR>This=20

    e-mail message (including any attachment) is intended only for the = personal=20

    <BR>use of the recipient(s) named above. This message is = confidential and=20

    may be <BR>legally privileged. If you are not an intended = recipient, you may=20

    not review, copy or <BR>distribute this message. If you have = received this=20

    communication in error, please notify <BR>us immediately by e-mail = and=20

    delete the original message.<BR><BR>Any views or opinions expressed = in this=20

    message are those of the author only. <BR>Furthermore, this message =

    (including any attachment) does not create any legally <BR>binding = rights or=20

    obligations whatsoever, which may only be created by the exchange = Received on Wed Jul 16 2003 - 07:02:19 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US