Determining "onstat -z"
Posted in 2004
Topics: General Discussion
Is there any way to programmatically determine if a "onstat -z" has
been issued? We run some analysis tools/scripts that log deltas for
things like IO and resetting the counts really skews the output.
Thanks,
Fred Prose
Fred Prose wrote:
> Is there any way to programmatically determine if a "onstat -z" has
> been issued? We run some analysis tools/scripts that log deltas for
> things like IO and resetting the counts really skews the output.
>
>
> Thanks,
> Fred Prose
Check the following column:
sysmaster:sysshmvals.sh_pfclrtime
HTH.
Best regards
Eric
--
IT-Consulting Herber
***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************
Eric Herber wrote:
> Fred Prose wrote:
>>Is there any way to programmatically determine if a "onstat -z" has
>>been issued? We run some analysis tools/scripts that log deltas for
>>things like IO and resetting the counts really skews the output.
>
> Check the following column:
>
> sysmaster:sysshmvals.sh_pfclrtime
And provide some mechanism to control who can issue 'onstat -z'?
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/
Jonathan Leffler wrote:
> Eric Herber wrote:
>> Fred Prose wrote:
>>>Is there any way to programmatically determine if a "onstat -z" has
>>>been issued? We run some analysis tools/scripts that log deltas for
>>>things like IO and resetting the counts really skews the output.
>>
>> Check the following column:
>>
>> sysmaster:sysshmvals.sh_pfclrtime
>
> And provide some mechanism to control who can issue 'onstat -z'?
>
Yes, that would be nice feature for a future informix
release. The fact that everybody is able to execute
'onstat -z' is a problem if you try to monitor the
instance and sampling data from the sysmaster database.
Also the DB2 approach where you can reset the current
counters (db2 reset monitor...) and it only affects your
own connection (because each connection has a private view
of this monitor data) is helpful.
However this might be difficult to implement for the
sysmaster interface.
Best regards
Eric
--
IT-Consulting Herber
***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************
Related threads
- IDS not writing to online.log
- Help!!! syntax error
- installclientsdk bug?
- RamDisk tempdbs boot script for Linux