RE: DB Processes which can be Killed ?

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Wed, 11 May 2005 08:19:40 -0400
Message-ID: <5A14AF34CFF8AD44A44891F7C9FF41050395B8BB@usahm236.amer.corp.eds.com>

No, you cannot just go by an INACTIVE value of the status column in v$session. If the front-end connection is an application like Oracle Forms that connects and stays connected by the user spends much of their time working on the front-end filling in data and moving between fields then the status will show INACTIVE while these events are taking place. You need to also look at how long since the session has submitted a request: last_call_et.

See the Oracle version# Reference manual entry for v$session.

HTH -- Mark D Powell --

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of VIVEK_SHARMA Sent: Wednesday, May 11, 2005 3:25 AM
To: oracle-l_at_freelists.org
Subject: DB Processes which can be Killed ?

A basic Qs:-

How to Identify Idle/Sleeping/Hanging session processes which are connected to the DB i.e. those that are useless?

Is it processes with v$session.status=3D3D"INACTIVE"?

Thanks=3D20

P.S. Hope I have been able to communicate my need.
--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Wed May 11 2005 - 08:24:33 CDT