Re: Identifying problem sql's via onstat

Steve Gould <sg@leaderflush.co.uk> wrote in article <884685991.19482.0.nnrp-03.9e987eaf@news.demon.co.uk>... > Has anyone written a unix or awk script > to identify the link between a running unix > processes and sql statements which are > effecting performance. I can manually run > onstat -u to give me the session id and> then onstat -g ses sessid to give me that > specific sql. But I can't identify the sessions > that are causing the greatest drag on > performance as they occur. Read/write > statistics from onstat -u don't show me > indexing/lock contention problems. > Thanks > Steve Gould Well, "onperf" has some good tools for finding the sessions which are using the most time, and from there you can find the SQL and even watch the query tree in real-time. But this is only good if you have an X server of some kind. (An actual X-terminal or PC running emulation software.) I have a script called "onact" which helps identify the most active suser threads. From there you can use onstat -g sql <session-id> to see the SQL statements. "onact" is available at http://www.objectsoft.com under "Informix Tips". HTH Irwin Goldstein Objective Software Systems, Inc.