Re: why frequent commits are not good?

No data object is locked.

If you 'select * from v$lock' you will find that the local database has taken out a TX lock in mode 6, and a DX lock in mode 4.

The requirement for a commit or rollback is nothing to do with the 'select' per se, and releasing data for other processes,
it is purely to release the transaction entry and tiny bit of space used in the rollback segment.

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



Frank wrote in message ...


>> Distributed SELECTS do start a local transaction.

>> If you NEVER commit, and stay connected

>> indefinitely, you will stop your rollback segment

>> from being .....

>

>Hi!

>

>I dont speak these lock-flags fluidly, so I wonder; what exactly is locked

>(see

>NetComrade's posting) when doing this query?

>

>select empno,ename from emp_at_remotedb;

>

>And does this raises a lock locally so that no other session on the local

>datababase

>can query the same remote table until commit/rollback?

>

>Frank

>

>