Folks,

Any opinions on Oracle's implementation using synonyms/database links for
distributed transactions. Can I assume that the two-phase commit works
particulary with respect to transaction rollback in the event of a failure.

Thanks,

With both versions 9.2 and 10g the DBA Administration Guide contains
several chapters on distributed processing. The Oracle rdbms
background process, reco, handles resolution of failed distributed
transactions.

Synonyms are not technically necessary for distributed transactions
since you can just code the remote owner.object_name@link in your SQL;
however, providing synonyms for remote objects makes codeing
distributed transactions easier for developers and end-users while
providing location transparity.

HTH -- Mark D Powell --

Rich,

One word of warning, two phase commits can, in the right conditions,
lead to big time scalibility problems. Jonathan Lewis has written a
paper describing the problem.
http://www.jlcomp.demon.co.uk/02_tpm.rtf. Hope this helps and sorry if
you already had this info.

John
Mark D Powell wrote:
> With both versions 9.2 and 10g the DBA Administration Guide contains
> several chapters on distributed processing. The Oracle rdbms
> background process, reco, handles resolution of failed distributed
> transactions.
>
> Synonyms are not technically necessary for distributed transactions
> since you can just code the remote owner.object_name@link in your
SQL;
> however, providing synonyms for remote objects makes codeing
> distributed transactions easier for developers and end-users while
> providing location transparity.
>
> HTH -- Mark D Powell --