When connected to an Oracle database, I am getting occasional messages from TDA that I have had a transaction open for a long time, and asks if I want to commit or rollback. However, I’ve only been running select queries, and haven’t done anything to update the tables.
I shortened the length of time for the timeout, just to test it out more, and also found that once the message pops up, if I just let the timer run down, although it says it is going to roll back the transaction, it doesn’t seem to, as the message will show up again a short time later (even though I’ve done nothing else in TDA).
Now, I am currently running version 2.5.1 (business policy prevents me from upgrading). However, I noticed in the release notes for 2.6, there was reference to a fix put in relating to the open transaction timeout. However, I’ve been unable to find any information on what that issue was, and if it’s related to what I’m seeing.
I’m still running some scenarios to gather data, but I thought I’d check and see if anyone had any suggestions.
Any information would be appreciated.