Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Better demonstration of the serious transaction bug in Oracle
HI,
here's my output on oracle novell 8.1.5 EE
so what exactly does this impact and how can it be worked around.
steve
Total Transactions
9
SQL> select count(*) "Correct Transactions" from isolationtest where val = 200;
Correct Transactions
8
SQL> select count(*) "Failed Transactions" from isolationtest where val != 200;
Failed Transactions
1
Bold <Bold_at_yahoo.com> wrote:
> Solaris 2.6
> Oracle 8.0.5
>
>
> Total Transactions
> --------------------
> 109
>
> SQL> select count(*) "Correct Transactions" from isolationtest where val
> = 200;
>
> Correct Transactions
> --------------------
> 104
>
> SQL> select count(*) "Failed Transactions" from isolationtest where val
> != 200;
>
>
> Failed Transactions
> --------------------
> 5
>
> Martin Haltmayer wrote:
>
> > Oracle 8.1.5, NT 4.0 SP 6a:
> >
> > Total Transactions
> > --------------------
> > 109
> >
> > SQL> select count(*) "Correct Transactions" from isolationtest where val
> > = 200;
> >
> > Correct Transactions
> > --------------------
> > 104
> >
> > SQL> select count(*) "Failed Transactions" from isolationtest where val
> > != 200;
> >
> > Failed Transactions
> > --------------------
> > 5
> >
> > Martin
> >
> > Joseph Weinstein wrote:
> > >
> > > Hi. While some folks were able to duplicate the Oracle transaction bug,
> > > At least one person did not, with the small simple script I sent. Here is
> > > a looping script which is much more compact, and intelligently written
> > > (not by me). This runs 1000 transactions, each one inserting a unique
> > > row to a table, then updating it. The bug is that the update part of the
> > > transaction may silently fail. I get:
> > >
> > > Total Transactions
> > > --------------------
> > > 1000
> > >
> > > Correct Transactions
> > > --------------------
> > > 821
> > >
> > > Failed Transactions
> > > --------------------
> > > 179
> > >
> > > If anyone would try this, and post their results, it would be very helpful
> > > In SQL-PLUS, enter:
> > > SQL>@bug.sql
> > >
> > > Thanks,
> > > Joe
Received on Thu Jan 27 2000 - 21:30:00 CST