Rick,
A distributed transaction normally uses the two-phase
commit process so all sites should either commit or
rollback. If there's a failure in one site then the
RECO process should automatically recover the
distributed transaction. Until it does this there
will be info in DBA_2PC_PENDING and DBA_2PC_NEIGHBORS
about the in-doubt transaction.
Does this behavior occur only through your application
or if you issue the sql for the distributed
transaction manually via sqlplus?
What are the versions of the db's involved?
For performance reasons db links remain open for the
life of the session, unless explicitly closed. To
close a dblink for a given session:
ALTER SESSION CLOSE DATABASE LINK db_link;
HTH,
-- Anita
--- [EMAIL PROTECTED] wrote:
Hi,
I'm executing DML to three remote sites. The
problem is that if there is a failure at a given
site (i.e. the last site), the first two are
commiting the transaction leavintg the third out of
sync.
We also noticed that the remote links stay
connected. Shouldn't they disconnect after the
transaction ends?
Any ideas to solve this problem would be greatly
appreciated. We are using version 8.0.5.
Thanks for your help.
Rick
__
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: A. Bardeen
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
