OpenEdge Explorer: Oldest Transaction Age - Forum - OpenEdge RDBMS - Progress Community

OpenEdge Explorer: Oldest Transaction Age

 Forum

OpenEdge Explorer: Oldest Transaction Age

This question is not answered

We are attempting to use the "free" version of OEM (called OEE) to troubleshoot the top 10 most common problems that we regularly encounter when trying to use the OpenEdge database in production.

One common issue is when long-running transactions take a record lock and the database is unable to enforce any reasonable timeout.   (Thereby requiring workarounds in the ABL programs themselves, or requiring manual intervention by an OE dba to disconnect misbehaving client program).

We hoped that this ("no reasonable timeout") problem could be diagnosed by a dba if they would simply refresh the "Database Performance Summary" screen under "Operational Views".  One symptom of the "no reasonable timeout" problem would be seen in the "Oldest transaction age" (under heading: "Record and Transaction Summary".)  This should be visible and should start to grow excessively long (10..30..60 mins).

Unfortunately we are *not* seeing any meaningful information for "Oldest transaction age".  It always remains blank for us.  Can anyone who uses OEE (or OEM) let me know if you have ever seen anything appear for this value?

Keep in mind that, with OEE, we are running a simple Monitoring Agent for  the database but no "monitoring plans" or "maintenance jobs".  I believe those are only available for the more advanced "OEM" product.

I am already aware that OEE is not a widely used product, and that Progress relies on third-parties (eg ProTop) to deliver better management tooling for their RDBMS.  However, I don't think that displaying the "oldest transaction age" is too great of a ting to ask for.  The only other place I am able to find such a thing is buried deep in the "R&D" menu of promon (R&D->1->4->3).  While digging around in promon is not the end of the world, we'd prefer it if all our top 10 problems could be diagnosed with one or two mouseclicks in OEE.

Any help would be appreciated.  

All Replies
  • OEM / OEE basically has kept the same monitoring functionality for the last 10 years, since OEM version 3.x

    In my experience OEE is useful for users that don't like the command line utilities to manage ubroker.properties or to start / stop an OE object.  I would not use it to track down problem users / programs.  A few fairly basic ABL programs can monitor transaction age and locking information.