Re: Monitor tools

You could go to the trouble of getting onperf going on your system, if you = like GUI tools, personally I find them inefficient. If you have a suspicion that you have a specific process that is hogging = resource the steps I take are to identify the active threads, then from = the threads identified go to the session, which gives you the PID the sql = being run , the user etc. These are the steps I use. 1. run onstat -g act several times over a minute or two. You get output = like this Running threads: = =20 tid tcb rstcb prty status vp-class name = =20 = =20 14 f120e20 0 2 running 1cpu sm_poll = =20 15 f134630 0 2 running 18tli = tlitcppoll =20 16 f134af8 0 2 running 19tli = tlitcppoll =20 These are just the poll threads. An active system process will show up = running against a vp-class of type cpu, and with a name of sqlexec EG 12345 fxxxxx 2 running 2cpu sqlexec The one that appears the most often over the minute or two is the = suspect. 2. To find out the session info for this guy you can put the following in = a ksh script and run it from the command line onstat -g ses `echo " =20 select us_sid from sysuserthreads where us_tid =3D $1 =20" | dbaccess sysmaster 2>/dev/null | grep -vi sid | sed '/^$/d'`=20 Pass it the thread id as a parameter and it will tell you the session = info. EG [Say you called your script] sesinfo 12345 HTH rgds Peter Tashkoff <tashkop@iname.com> Zespri International Limited Std Disclaimers Apply All rights reserved. No party may use this document to vilify another. Zespri New Zealand Kiwifruit, The World's Finest >>> "Eric Urff" <urff@dbcc.cc.fl.us> 13/05/98 03:41:44 >>> Are there any good tools to monitor the performance of Informix. We are = running 7.2 on HP-UX and the engine has a tendency to go a crawl and there = appears to be no way to decipher the culprit easily.. Any ideas? Eric Urff urff@dbcc.cc.fl.us=20 Director of Information Systems Daytona Beach Community College (904)253-3026