D
dbeavon
Guest
Wow, based on your screenshots it looks like the problem developed over the course of 3.5 hours. Does that sound right? I sure wish OE had some sort of reasonable transaction timeout which could be enforced by the DBMS itself. This problem happens to us regularly. There are a few factors that are typically involved. It normally stems from the interactive CHUI users who have open transactions that use pessimistic record locking. The CHUI user may go to lunch without remembering to close out of their OE database transaction. The OE dba then steps away for a few hours as well, and nobody gets alerted about BI growth, nor long-running transactions. Then the problem slowly escalates into a system-wide issue as other similar CHUI users, or batch processes start to become backlogged on the same locked records. This problem is something we were hoping to be able to troubleshoot with OE Explorer's "oldest transaction age" property. I think the transaction age is even more important than the BI usage, since it is the initial indicator that something is going wrong, and you can start sending out alerts long before BI grows to 2 GB. (Assuming transactions shouldn't legitimately last for hours at a time.) Unfortunately the "oldest transaction age" doesn't seem to be reported properly in OEE. I just asked about this earlier today: community.progress.com/.../36140
Continue reading...
Continue reading...