Informix HQ does not display "Current SQL statement" or "Last parsed SQL statement" for session unless sql trace is turned on.Is this bug or feature?Some customers have 100.000s statements per second and turning sql trace on will keep just last 0,05 seconds of sql commands (unless you put 400GB for sql trace buffer - so you have to kill your server to monitor it - call me crazy but this is crazy)
Why HQ does not use sysmaster tables (as onstat -g sql does)?RegardsHrvoje
Thanks Art - I know that, their DBA knows that. But, as I explained some of users (app/dba users) are making some ad hoc queries. And when they realize it is lasting for a long time, they open OAT, locate their session (looking for query) and then terminate that session. This is simple explanation, there are some more events when they terminate their own session. And there is task for killing long lasting sessions (if I remember right). But sometimes they want session to last as long as it takes.
So, I know I can do it, DBA can do it - but then they would have one person assigned to killing sessions - since sometimes it is urgent to kill such a session and DBA is doing other stuff besides DBA and I have to jump through couple of vpn-s, log to vpn, ask for access, ....
The simplest way is that users kill their own session. They are not even logged on DB server - they use different frontend tools.
I think if HQ will not show these data they will have to turn sqltrace on for that users - but I miss that from OAT :)Hrvoje
Hi Hrvoje,we have this feature in our Admin-Scout. It is possible to sort on every column and such sessions are killable directly.
Here the report in our online demo: https://scout-demo.cursor.de/openadmin/index.php?act=home&do=sessexplorerRegardsErik