> A number one reason for a stuck OAT can be transaction which has been
> *committed* with COMMIT RETAINING. Funny, right? Committed but still
> active. ;-)
>
> Data access components tend to use commit retaining aka soft commits,
> especially when being in autocommit mode.

My components are set to:

Commit Retaining = OFF
Isolation Level = ReadCommited

Which AFAIK is the best setup, so..

Is there a way to verify in the database that the transactions are
created following this parameters?
I believe I could use the monitoring tables in 2.1+, right?
What about 2.0?

--
Erick Sasse