Well, the other option is to start developing apps and test them using
larger data sets then available in EMP and DEPT tables. Even with full
table scans, everything seems to work miraculously on those tables.
On 2003.07.16 08:59, Lee Cullip wrote:
> 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.
>
> Cheers
> Lee
>
>
> -----Original Message-----
> Sent: 16 July 2003 11:19
> To: Multiple recipients of list ORACLE-L
>
>
>
> 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ércoles, 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).
>
> Hope this helps.
> Cheers
> Lee
>
> -----Original Message-----
> Sent: 16 July 2003 09:09
> To: Multiple recipients of list ORACLE-L
>
>
>
> 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.
>
>
> -----Mensaje original-----
> De: venkat Rama [mailto:techsqlca_at_yahoo.com]
> Enviado el: miércoles, 16 de julio de 2003 6:34
> Para: Multiple recipients of list ORACLE-L
> Asunto: Rollback Segs
>
>
> Hi Friends,
>
> 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.
>
> Any help will be appreciated
> Thanks
> venkat.
>
>
>
>
>
>
>
> _____
>
> Do you Yahoo!?
> SBC
> <http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*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
> 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
> distribute this message. If you have received this communication in error,
> please notify
> us immediately by e-mail and delete the original message.
>
> Any views or opinions expressed in this message are those of the author
> only.
> Furthermore, this message (including any attachment) does not create any
> legally
> binding rights or obligations whatsoever, which may only be created by the
> exchange
> of hard copy documents signed by a duly authorised representative of
> Hutchison
> 3G UK Limited.
> ________________________________________________________________________
Received on Wed Jul 16 2003 - 07:15:12 CDT
