RE: what does info from onstat -g ses xxx indicate here

I have run into the same thing, I believe that if the program hasn't closed the cursor, that it still shows up as the current SQL. In other words, until all the data has been returned to the user, it is the current sql statement. It is waiting for the user to request more data. Quite a few of the databases I am involved with exhibit these symptoms. Sometime the O/S is 99% idle. I now ignore sm_read and netnorm as far as considering them as queries which are currently being processed by the database. You can duplicate this situation by doing a select in dbaccess and not fetching all of the rows, then in another session doing an onstat -g ses <ses id>. You can write a program if you are more ambitious than me :) Hope this helps Will >===== Original Message From "Tam McLaughlin" <tamm@scotlegal.com> ===== >From what i know so far, this thread looks like its waiting on user input. >But just seems to be a simple query that is taking ages. Apparently the >developer done "set isolation dirty read". >Any ideas ? > > >session #RSAM >total used >id user tty pid hostname threads memory >memory >925 gregor pts013 2571 venus 1 73728 >7184 > >tid name rstcb flags curstk status >985 sqlexec ac27c4c Y--P--- 572 ac27c4c cond wait(netnorm) > > >Current statement name : slctcur >Current SQL statement : >select mast_pol_num from pal_obmast where (mast_allocated="N" or>mast_allocated="Y") and mast_tab_num="329" ------------------------------------------------------------ This e-mail has been sent to you courtesy of OperaMail, as a free service from Opera Software, makers of the award-winning Web Browser, Opera. Visit us at http://www.opera.com/ or our portal at: http://www.myopera.com/ Your free e-mail account is waiting at: http://www.operamail.com/ ------------------------------------------------------------