Hello Jason,

>> One thing is, if you only read data, then use a read-only transaction.
>> In combination with the read committed isolation level, you are in a
>> transaction mode with very low overhead and OIT/OAT won't get stuck as
>> well, even for long runners.
>
> It might also be helpful to make use of a relatively new feature I added to
> IBO that enables you to separate your transaction handling between two
> physical transactions. One is for reading only and the other is for your
> updates and individual record synchronizations. The new property is called
> IB_TransForUpdate.

Thanks for letting me know.


Regards,
Thomas