Tested
Sandeep Shenoy, February 29, 2012 - 7:06 am UTC
Hi Tom,
Thanks for your reply. I have tested it using the following steps.
open a session s1
Run the following scripts from s1
CREATE TABLE T1
( ID1 NUMBER(9,2) primary key,
NAME1 VARCHAR2(100));
insert into t1 values(1,'Tom');
commit;
open a new session s2
Run the following commands from s2
Set transaction isolation level serializable;
select * from t1;
from session s1 run the following command
delete from t1;
commit;
from session s2 run the following query
select * from t1;
--1 row will be returned as the result though it has been deleted from the table. Run the following commands now from s2
commit;
select * from t1;
---no rows will be returned which means if the isolation level is serializable (this is read committed by default in oracle), then we have to commit if we want to see the changes done by other sessions on the database.
But in Distributed environment, if the other database is also an oracle database. what's the need of ending the transaction using a commit or rollback. Because the isolation level is read committed by default in oracle and i am not setting the isolation level as serializable explicitly. But still, we have to commit or rollback if we select from a table using a database link. Can you explain with an example.
Thanks in advance.
February 29, 2012 - 7:48 am UTC
simple question
napa, August 09, 2012 - 12:47 am UTC
how to rollback commited transaction in oracle.
pls give the example.