"~Setup an alert to notify..."
You're missing the "n" after "~".
Q: Is there a limit to how minor a bug I will report?
A: There is not.
Are you trying to run ProTop in a maximized proenv session?
Does it keep resizing on you to 160 x 48, no matter what you do with the Layout tab in proenv Properties?
Have you pulled out most of your hair?
Here's the tip:
(Somewhat off-topic): That KB list is pretty close to a list of my own that I've been updating off and on over the years. I stopped updating mine when, thankfully, I got rid of my last WG license.
However to me this looks questionable, re licensing requirements for TDE:
OpenEdge Enterprise RDBMS and OpenEdge TDE or alternatively Advanced Enterprise Edition RDBMS available since OpenEdge 11.5 (for Production) OpenEdge Development Server (for Application deployment)
I don't see what OE Dev Server has to do with TDE. It is the development version of App Server, is it not? Same goes for the footnotes for MT and TP.
Also, aren't -napinc and -napstep decommissioned?
I'm looking at the numbers from a client site and they don't make sense to me. At a given time stamp today, I see the following user connection counts:
I know this client has self-service users. I believe that most if not all of those 30 batch users are also self-service. Looking at historical data, most of the time this database shows zero self-service users, with occasional spikes of 1.
What criteria are used to determine that a client is self-service?
It seems the dashboard layout changed recently.
I am looking at "Main Dashboard" for a monitored database. I have the following panes:
There used to be panes for BI and AI info. Have they been relocated? Will they be returning?
case _Connect-type: ... when "sqsv" then tt_Dashboard.con_sqlServ = tt_Dashboard.con_sqlServ + 1. ... end. //case if _Connect-type begins "SQSV" then tt_Dashboard.con_SQLServ = tt_Dashboard.con_SQLServ + 1.
This may also be in previous versions; I haven't checked.
Regarding the specific alert: there is a lkTblPct field which I use for a similar purpose. Rather than the HWM it reflects the locks in use at that moment. In some ways that is better -- the HWM sticks around until you restart and if something went bump in the night is going to keep alerting once you hit the threshold.
Good to know, thanks.
Maybe this belongs in "Roadmap" rather than "Using", but anyway...
Looking at alert.cfg:
# # Metric Type Compare Target Sensitivity Notify Message Action # ====== ==== ======= ====== =========== ====== ==================== ======================= # LogRd num > 100000 3:5 Always "Hit Ratio &1 &2 &3" alert-message,alert-log # # Metric The ui-det name of the field being monitored. # # Type Data type -- char or num (string or numeric). # # Compare Operator -- >, <, =, <>, <=, >= # # Target The threshold value of the metric to be tested.
Since it isn't stated explicitly, does "Target" have to be a constant? Could it be another metric of the same data type as "Metric"? Or an expression on constants or metrics (e.g. lkHWM * 0.8)?
Use case: let's say I want to configure an alert to fire when the lock HWM is getting close to -L, and have it work regardless of the value of -L, which could possibly vary over time or from one DB to another. Is that possible? Or do I just need to decide which number (say, 7000) I care about and configure it to alert when lkHWM > 7000?
Food for thought: the alerting mechanism would become more powerful if the target values could be dynamic in some way. Maybe passed to the back end via the API.
For reference, the non-essential audit indexes (which are often purposely deactivated, except in audit archive DBs):