Re: How to trace ODBC connection?

Perhaps onstat -g sql or onstat -g ses may help. At least that will show you the SQL statement that preceded the long transaction rollback. Andy miyaki <lcib@yahoo.com> wrote in message news:<bv245a$f5m$1@terabinaries.xmission.com>... > Hi all, > > Most of our applicatoins were developed in Windows/Web > platform and they are accessing my database via ODBC > type of connection. I found that it's very difficult > to trace the problem caused by the ODBC connection, > especially from the Web based application. From the > output of onstat -u, i can only see the tty and login > id. However, the tty and login id is the same for all > the connections from a particular Web application. For > instance, i have over 100 concurrent users using a web > application that connected to my database via a Web > server. During that time, a LONG Transaction occured > which is caused by one of the 100 concurrent users. In > this case, I'm not able to catch the the real user > that causing the problem as the output of onstat -u is > showing the same login id and tty. I believe some of > you guys also experience this type of situation > before. Hence, apppreciate that if you could share > with me how you handle this type of problem. > > BTW, here's some info pertaining to my database > server. > > OS = Solaris 2.7 (x86 platform) > IDS = 7.31UC2 > > Thanks, > Miyaki > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free web site building tool. Try it! > http://webhosting.yahoo.com/ps/sb/ > sending to informix-list