Encina, XA, Oracle 8.0.4, Distributed database, MTS

Does anyone have experience of the above. I have come across a very strange problem.

Our setup is:

Encina as a TPM, using XA calls to Oracle. For location transparency, the Oracle database addresses is actually a collection of databases with database links.

The Encinca code is written in Pro*Cobol, and updates Encina Queues and Oracle
tables in a single transaction.

Oracle is running with MTS (a necessity when using database links and Encina).

The problem:

A loop moves data across Encina queues, and inserts into the local Oracle database, and the remote Oracle database then commits
(with a tx_commit).

On the first pass everything works perfectly, on the second pass, the local commit clearly takes place - TADDR goes null in v$session, the entry in V$transaction disappears, and the data become visible to other sessions,

BUT --- the remote database does NOT commit,
and the transaction stays open and is
re-acquired by the next pass of the loop.

Result: complete loss of data integrity.

Any clues, anyone ?

(Any email replies will be summarised and
posted to the group).

--
Jonathan Lewis Received on Thu Jul 02 1998 - 16:39:40 CDT