RE: Rollback Segs

[Lee Cullip]

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-----
From: Fermin Bernaus [mailto:[EMAIL PROTECTED]
Sent: 16 July 2003 09:09
To: Multiple recipients of list ORACLE-L
Subject: RE: Rollback Segs

 

    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:[EMAIL PROTECTED]
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 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.
________________________________________________________________________