Vinit:

I thought the same ... but there is a problem. My scripts that show the users show the Unix proc id#. The web connections don't show as Unix proc# - just the port #:

-------------------------------------------------------
CQ05 / cqweb dllhost.exe-NTS31(ERDSE087\NTS 13/53909 INACTIVE 1632:296 22-NOV-2001:15:53:28 19:35:59
31 ) /
22-NOV-2001:15:54:07
-----------------------------------------------------

This previous is the result from a script that uses:
V$SESSION

As you see the "Unix process" is shown as "1632:296" which are the port numbers NOT the Unix procs. The script does however work to show "Unix Procs" when run on a normal(non web) sql connections as shown here:

--------------------------------------------------------
ROGER / oracle [email protected] 12/9327 INACTIVE 17024 23-NOV-2001:11:33:34 00:00:28
e (TNS /
V1-V3)-pts/3(ora04.era-a.erics 23-NOV-2001:11:33:33
son.se)
-------------------------------------------------

So, the problem is that I can't identify the correct Unix procs to kill off when dealing with web connections that leave Unix procs after being killed with kil session.

Catch 22 - Rational says I should kill them manually but I can't readily identify them. If they were normal SQL connects I could easily see the Unix Proc and create a script to cleanup.

This is a bit strange but a real problem.

-Roger