SMI query
Posted in 1999
Hi Folks,
We are in need of enlightenment and help !!!
We are trying to establish a method of tracking the time taken by an
individual SQL statement within Informix IDS 7.30.UC6. Ideally we would
like to achieve this by accessing the SMI tables direct. However, if
this is not possible then using the onstat commands as a basis for shell
script interrogation is an acceptable second best.
Because of our particular circumstances we need to be able to do this
independently of any process running. In effect we are looking to create
a method of checking for problem SQL while production code is running.
So far we have concentrated on the following in our search but do not
seem able to break things down to sufficient detail.
Other SMI tables and onstat commands have been researched but the
following proved to be the most useful to date.
SMI Tables
sysconblock,
syssessions,
syslocks,
flags_text
Onstat Commands
onstat -u
onstat -g ath
onstat -g ntt
onstat -g ses SID
The most common problem with the above is that they hold details for the
life of the connection not just the SQL.
Hence the following:-
1). sysconblock seems to hold details of an SQL that has run and
completed until the connection is broken.
2). An interactive 4gl can be started and then left open for an hour
then used again.
The time values shown by onstat -g ntt includes the fallow hour.
If anyone has detailed information on the undocumented SMI tables or has
already succeeded in solving this problem we would be delighted to hear
from you.
Many thanks for any assistance in this matter!
--