Re: WARNING: if you ever want Oracle serializable transactions to be safe

On Tue, 18 Jan 2000 01:56:56 +0100, Joseph Weinstein <joe_at_weblogic.com> wrote:

>
>Hi. I have verified with Oracle that there is a longstanding bug in the Oracle
>DBMS, which may cause transactions with SERIALIZABLE isolation level
>to silently fail. This affects EJBs as well as any other transactional client.
>
>The bug arises in transactions where a given row is inserted then updated
>within a single transaction. The update may silently fail. This is a common
>EJB scenario.
>

But, you need to understand the context of the bug -- it does not simply apply to all cases where TRANSACTION ISOLATION is set to SERIALIZABLE (which is what you are implying).

> Tech support has told me that the bug (Oracle bug #440317) has been
>repeatedly put off being fixed (since Jan '97) because of the scope of work
>involved in fixing it.

True.

>
> If you might be affected by this bug, you should contact Oracle support about
>Oracle bug #440317, and add your concern to the case. Only when there is a
>critical mass of awareness and concern will Oracle feel justified in committing
>the resources to this issue.

Also true. When you contact them, have them explain the context in which you might encounter the bug. Received on Tue Jan 18 2000 - 19:17:27 CST