Re: Remote Select opening transaction
- From: Hemant K Chitale <hkchital@xxxxxxxxxxxxxx>
- To: marc.demlenne@xxxxxxxxx, oracle-l@xxxxxxxxxxxxx
- Date: Tue, 03 Apr 2007 21:52:31 +0800
A distributed query is always treated like a distributed "transaction", with
the inherent two-phase commit mechanism.
See http://www.jlcomp.demon.co.uk/faq/dblink_commit.html
or the Chapters on Distributed Transactions in the Administrators Gu9ide.
The read-consistency model within an instance relies on the SCNs in
the instance.
When you are running queries across two database instances that ARE running
different SCNs, how do you get read consistency ? I believe that the
distributed
transaction method of using the highest global SCN is used for queries as well.
Hemant
At 08:07 PM Tuesday, Marc Demlenne wrote:
Hello,
In Oracle 8, when performing a select query on another database
threw DB link, Oracle opens a transaction that could only be closed
by commit or rollback. That could be harmful when developers are not
aware of this and don't close transaction. (leading to ORA-01562.)
What is the reason of this behaviour ? Is there some docs / faq
explaining this ?
Is this feature also common to later versions of Oracle ?
Thanks a lot for any piece of information given,
--
Marc
Hemant K Chitale
http://web.singnet.com.sg/~hkchital
and
http://hemantscribbles.blogspot.com
and
http://hemantoracledba.blogspot.com
--
http://www.freelists.org/webpage/oracle-l
- References:
- Remote Select opening transaction
- From: Marc Demlenne
Other related posts:
- » Remote Select opening transaction
- » RE: Remote Select opening transaction
- » Re: Remote Select opening transaction
- » RE: Remote Select opening transaction
- » Re: Remote Select opening transaction
- » Re: Remote Select opening transaction
- » RE: Remote Select opening transaction
- » Re: Remote Select opening transaction
Hello,In Oracle 8, when performing a select query on another database threw DB link, Oracle opens a transaction that could only be closed by commit or rollback. That could be harmful when developers are not aware of this and don't close transaction. (leading to ORA-01562.)
What is the reason of this behaviour ? Is there some docs / faq explaining this ?
Is this feature also common to later versions of Oracle ? Thanks a lot for any piece of information given, -- Marc
- Remote Select opening transaction
- From: Marc Demlenne