Serializable transactions

From: Thomas DAVID <tdavid_at_icway.com>
Date: 2000/06/05
Message-ID: <393B81FC.CEE5F2C6_at_icway.com>#1/1

Hi all,
I am experiencing troubles with the Serializable transaction on an Oracle 8.1.5 server. It's running on a linux RH6.1. The implementation of serializable transactions seems to be quite strange. It is supposed to pervent inconsistency of data. But this small example shows strange behavior of Oracle. [Quoted] [Quoted] The transation are executed in seperate clients, and the first one uses the default oracle setting "read committed". transaction 1:
SQL> select * from ref_table_1;

        ID TOTO TITI PARAM_CREA PARAM_STAR PARAM_ENDA ---------- ----- ---------- ---------- ---------- ----------

         1 eheh          15 05/03/2000 01/01/2000 04/30/2000
         2 eheh          15 05/03/2000 05/01/2000 09/30/2000
         3 eheh          15 05/03/2000 10/01/2000

transaction 2:
SQL> set transaction isolation level serializable; Transaction set.

transaction 2:
SQL> delete from ref_table_1 where ID=3;

1 row deleted.

SQL> commit;

Commit complete.

transaction 1:
SQL> delete from ref_table_1 where ID=2; delete from ref_table_1 where ID=2

            *
ERROR at line 1:
ORA-08177: can't serialize access for this transaction

Does someone has something to make all this clearer? Thoms Received on Mon Jun 05 2000 - 00:00:00 CEST