Re: monitor user processes

I think that if you see the process listed as active you're pretty safe in assuming that it is. A much more likely case is to see a process listed as inactive (at the moment you looked) even though it's still running.

Van

Steven Cardinal <scardinal_at_yahoo.com> wrote in message news:7sb6fq$ngb_at_chronicle.concentric.net...
> Is there anything that would also show io or cpu - I guess I don't trust
> that just because the process is active, that it's still chugging along
> (although maybe my experience with MS-SQL has me pessimistic - there, i
> would see an active state even though the job has hit a wall)
>
> Thanks
> Steve
>
> Jeff Hunter wrote in message <37e91a83_at_defiant.btitelecom.net>...
> >SQL> l
> > 1* select sid, serial#, program, username, status from v$session
> >
> > SID SERIAL# PROGRAM USERNAME STATUS
> >--------- --------- ------------------------------ ------------ --------
> > 116 2733 MSACCESS.EXE LOSHERRYM INACTIVE
> > 118 1088 MSACCESS.EXE LOKIML INACTIVE
> > 119 2271 sqlload_at_excelsior (TNS V1-V2) CALLREC ACTIVE
> > 120 7432 MSACCESS.EXE LOPATRICIM SNIPED
> > 121 1831 MSACCESS.EXE LOGILLIANC SNIPED
> > 122 1973 MSACCESS.EXE LOKARLETTH INACTIVE
> > 123 3281 MSACCESS.EXE LOCLAUDIAH INACTIVE
> > 124 1963 MSACCESS.EXE LOGERALDIG INACTIVE
> > 125 5183 MSACCESS.EXE LOKIMBERLB INACTIVE
> > 126 1701 MSACCESS.EXE LOTRACEYB INACTIVE
> >
> >
> >Steven Cardinal wrote in message <7sb4sq$men_at_chronicle.concentric.net>...
> >>What's the easiest way to monitor a user process to see if it is still
> >>performing work? Sometimes a process takes longer than expected, and we
> >are
> >>unsure if it is hung, or just working slowly. MS-SQL has a stored
> >procedure
> >>called sp_who2 that will show me cpu and io usage - if we run this
> multiple
> >>times and those number get larger we know things are still moving - how
do
> >I
> >>get the same kind of info out of 8.0.4 or 8.0.5 ?
> >>
> >>Thanks
> >>Steve
> >>
> >>
> >
> >
>
>
Received on Wed Sep 22 1999 - 19:58:41 CDT