2-phase commit queries and the Web Development Toolkit

Some developers here ran into a bit of a problem, when they submit queries
via db link the transactions always end up as 2-phase commit transactions.

This impacts our production server, because if one side cuts the connection
entries remain in dba_2pc_pending. Result is that the production db keeps
trying to re-submit these queries, to conclude the transactions.

Oracle has told me probably they need to put SET TRANSACTION READ ONLY
before every query that goes through a db link.

I don't know if that is a practical solution for pages built using the Web
Development Toolkit.

Another possible solution (?) might be to set the target tablespace to be
READ ONLY.
Has anyone else run into this situation? Have you found another workaround
for this?

To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).
Received on Fri Jul 19 2002 - 14:28:31 CDT