Question: Why do I get an ALERT #28 - Long transaction when there are no connections running long transactions?
Answer: If Foxhound is running on one computer and the target database on another, and you see occasional
false ALERT #28 - Long transaction messages, each one eventually followed by an ALL CLEAR #28
message, it is possible that the system clock is slowly drifting forward and then resetting on
the computer running Foxhound.
Foxhound requires the CURRENT TIMESTAMP values from both computers, and in this one case (detecting
a long transaction) Foxhound does not properly account for the difference in values.
This problem will be fixed in a future free upgrade of Foxhound.
You will be able to download and apply that upgrade without losing any of your data.
The Alerts Criteria Page - Alert #28