successfully ends.
Note that catalog table updators are DDL, not DML.
I think that's why Oracle commits on execution of every DDL.
"Kangmo, Kim" <[EMAIL PROTECTED]> wrote in message
ahple2$1rgh$[EMAIL PROTECTED]">news:ahple2$1rgh$[EMAIL PROTECTED]...
> I guess
I guess two transactions updated a tuple concurrently.
Because versioning scheme allows old versions can be
read by another transaction, the old version can be updated too.
For example,
We have a row whose value is 1
create table t1 (i1 integer);
insert into t1 values(1);
And,
Tx1 executes up
