Re: Bug in oracle 8.1.7 on Win2000server

Adrion-Weber wrote:

> Hi all,
>
> yesterday I had a really "funny" adventure.
> there is a server Win2000 with oracle 8.1.7 SE 2 instances with about 1
> G virtual memory on each.
> RAM is 2 GB.
> in one instance I had a failure found by a check routine in the
> application.
> so I detected, that a column in a row was not updated.
>
> So I tried to do it manually.
>
> following sequence of SQL-statements (in SQLPlus):
> 1.SELECT amount FROM DELIVERY WHERE DeliveryNo = 123456 ;
> AMOUNT
> ========
> 585.12
>
> 2.UPDATE DELIVERY SET amount = 653.88 WHERE DeliveryNo = 123456 ;
> Row updated
>
> 3.SELECT amount FROM DELIVERY WHERE DeliveryNo = 123456 ;
> AMOUNT
> ========
> 653.88
>
> 4. commit;
> Transaction comitted.
>
> 5.SELECT amount FROM DELIVERY WHERE DeliveryNo = 123456 ;
> AMOUNT
> ========
> 653.88
>
> 6.SELECT amount FROM DELIVERY WHERE DeliveryNo = 123456 ;
> AMOUNT
> ========
> 653.88
>
> 1.SELECT amount FROM DELIVERY WHERE DeliveryNo = 123456 ;
> AMOUNT
> ========
> 585.12 <=== the old value reappears after a few seconds (about 5-10)
>
> together we are three persons who saw this bug on a production database.
>
> we could reproduce this several times.
> after database shut down and startup again the bug disappeared.
>
> How can I trust a "bank", even a "datenbank"(=database ?)
>
> regards Berni

I've done enough work with 8.1.7 on Win2K that I'm not buying it.

Use log miner to view the logs and see what is really happening.

Daniel Morgan Received on Fri Feb 21 2003 - 15:20:02 CST