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

Home -> Community -> Usenet -> c.d.o.server -> Re: Better demonstration of the serious transaction bug in Oracle

Re: Better demonstration of the serious transaction bug in Oracle

From: Martin Haltmayer <Martin.Haltmayer_at_0800-einwahl.de>
Date: Tue, 08 Feb 2000 12:45:46 +0200
Message-ID: <389FF3DA.11AAFDC2@0800-einwahl.de>


If you put it two lines higher then only your first transaction is running in serializable because then you do a commit inside the for loop. The next time your loop is executed there is no setting to serializable again.

Martin

mligac_at_my-deja.com wrote:
>
> Hi,
> I tried it on Oracle 7.3.4 for NT and get 821:179 result. Reading
> manual (Oracle7 Tuning, release 7.3.3) I found in chapter this
> (Transaction Modes) interresting sentence: <font
> color="#FF0000"><b>!!!! If you wish to set the transaction isolation
> level, you must do so before the transaction begins. !!!! </b></font>
>
> So I tried to move SET TRANSACTION ISOLATION LEVEL SERIALIZABLE two
> lines higher, before the BEGIN, and results were OK (1000:0)!!!
>
> Hope this will explain "serious transaction bug in Oracle", if no
> please feel this just like a newbie answer.
>
> mligac
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Tue Feb 08 2000 - 04:45:46 CST

Original text of this message

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