@jcb Thank you so much, both for the very quick bug fix and also the cleanup of the stuck Outages!!

$PROTOP/etc/NOTES_*.

tick, tick, tick... The time for pre-release feedback is drawing to a close!

Thanks for that! (I had not noticed the scrollbar.) F3 seems like an odd key to be having any sort of impact at that point. I wonder if the "anykey" key also works

@tom said in Installation Instructions: Would be a better error message? Sure

@peter-whybrow said in Dashboard information: Also...how can I tell who and where a user is logged on from a Remote connection? The "W" (upper case) command will bring up a list of users and show the server IP address. If you need a specific user use the "#" command, set the usr# and then use the "U" command to look at that user's details.

if ( not _Connect-device matches "*batch*" ) and _connect-batch <> "yes" then tt_Dashboard.con_self = tt_Dashboard.con_self + 1. So "self" is counted for non-batch self-service connections. It (mostly) equates to local interactive connections. Somehow I suspect that you are going to suggest that that might be sub-optimal

@tom Sorry... off to the coffee machine...

Looks like it dates back to pt3.3n. It is fixed now.

@tom said in Alert re lkHWM near lkTableSize: 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.

Nope. You're right -- that's a bit more difficult to calculate and it seems much less likely. But I'll add it to the "think about it" list

Portal v4 has a lot of enhancements to stuff like this. Real Soon Now.

Which reminds me of another needed alert "not having audit archive db"

I think I probably need more visuals. I'm not forming a picture in my head of what you are describing.

Should be fixed in pt3.141x. I decided to simply use the first part of the device name unless the device name is "batch" and only if the name is otherwise blank. If that fails then use the usr#.

This is almost always for one of these reasons: The -tablerangesize or -indexrangesize parameters are not set to cover the active tables & indexes. The ChUI "T" command will show you what values are recommended and create a sample .pf file for you in the ProTop temp directory. Unfortunately you cannot change these values online. A db restart will be needed. The activity on the tables and indexes does not meet the threshold criteria. You can review the thresholds on the portal "Resource" screen. For development and test environments you probably want very low values. For Production you want higher values -- a chart with 2,000 objects on it will be unusable (that is why we have a minimum activity threshold). You should also verify that etc/pt3agent*.cfg has the TableActivity and IndexActivity data collectors enabled. If they are missing from ptInitDC then that data is not being sent to the portal.

That didn't take long! Thanks for the tip, I'll look into it

@tom said in OE 12 support: Lastly, I also (sneakily) patched the pt3.14 release a week or so ago. If your "as of" date on that is in May rather than March then you should also have the oe12 changes (but not the "4" hotkey). That explains it, I got the error from the original March version.