I think in some databases where reads lock writes, select is considered to lock a transaction. I think SQL Server used to work this way, but with SQL Server 2005 they added some form of Multi-Versioning. Transactions only involve changes to the data. Mark: I didnt know a select started a transaction when you access a remote object. That is interesting. So you actually get an SCN off a select in the redo logs when you select across a database link? I guess this is for the 3 phase commit process. -------------- Original message -------------- From: Jonathan Knight <knightjck_work@xxxxxxxxx> > We've scoured the documentation and are still a little fuzzy :-) on this ... > > We're trying to convert some SQL*Loads from conventional to direct and the > Oracle Documentation states that one of the requirements is that there are no > active transactions on the destination table. Obviously SELECT ... FOR UPDATE > would begin a transaction, but what about a simple SELECT? > > > Many thanks, > Jon Knight > > > > ________________________________________________________________________________ > > ____ > We won't tell. Get more on shows you hate to love > (and love to hate): Yahoo! TV's Guilty Pleasures list. > http://tv.yahoo.com/collections/265 > -- > //www.freelists.org/webpage/oracle-l > >