SEO

Dear all,

I am having a question here. hope you guys could help. Whenever
i kill a user, i cant kill the oracle statement there, eventhough the user
had been killed. What should be the problem? Does this mean that at the
background that session still running? I encountered system slow down
problem recently and cause me to kill the user whoever using the sesssion.
Please help. Thanks



Rgrds
Feei Shun

The Session will rollback all the active transaction once u kill the
sessions.

HTH

--
Cheers,
Ganesh Raja
==============================================
Live to learn ... Forget ... and Learn Again
==============================================


"Yong Feei Shun" <yong_feei_shun@uac.com.my> wrote in message
news:4047dfd9$1_2@news.tm.net.my...
> Dear all,
>
> I am having a question here. hope you guys could help.
Whenever
> i kill a user, i cant kill the oracle statement there, eventhough the user
> had been killed. What should be the problem? Does this mean that at the
> background that session still running? I encountered system slow down
> problem recently and cause me to kill the user whoever using the sesssion.
> Please help. Thanks
>
>
>
> Rgrds
> Feei Shun
>
>
>

Assuming you don't use the Oracle Multi-Threaded Server option (MTS) and
every process(Unix) or thread(Windows) is spawned on behalf of only 1 Oracle
session, then on NT use orakill to kill the problem thread and on Unix just
issue a kill command on the problem process .

--

"Ganesh Raja" <ganesh.raja@nospam.logicacmg.com> wrote in message
news:newscache$kx33uh$ooc$1@animal.logica.co.uk...
> The Session will rollback all the active transaction once u kill the
> sessions.
>
> HTH
>
> --
> Cheers,
> Ganesh Raja
> ==============================================
> Live to learn ... Forget ... and Learn Again
> ==============================================
>
>
> "Yong Feei Shun" <yong_feei_shun@uac.com.my> wrote in message
> news:4047dfd9$1_2@news.tm.net.my...
> > Dear all,
> >
> > I am having a question here. hope you guys could help.
> Whenever
> > i kill a user, i cant kill the oracle statement there, eventhough the
user
> > had been killed. What should be the problem? Does this mean that at the
> > background that session still running? I encountered system slow down
> > problem recently and cause me to kill the user whoever using the
sesssion.
> > Please help. Thanks
> >
> >
> >
> > Rgrds
> > Feei Shun
> >
> >
> >
>

feei Shun,
Some sessions dont go off so easily.
They will be marked as killed and will be cleared on later by PMON or
SMON.
If the killed session has done a big transaction, you can see the
rollback of the transaction activity by using this query. (How much is
being rolled back etc).

select ktuxeusn,ktuxeslt,ktuxesqn,ktuxesiz
from x$ktuxe
where ktuxecfl='DEAD'
/

select pid,state,undoblocksdone
from v$fast_start_servers
/

select usn,state,undoblockstotal,undoblocksdone,cputime
from v$fast_start_transactions
/
set feedback on

Sometimes the session may be doing a large sort and hogging up a lot
of CPU.
Then i find it better to kill the server background process relating
to that session.

After killing the session at Oracle level using alter session, you can
use this query to find and kill the background server process
associated with the dead session.

col cprogram form a30 trunc head "Client|Program"
col sprogram form a30 trunc head "Server|Program"
col sid form 9999
col pid form 9999
col process head "Client|Process|ID" form a10
col spid head "Oracle|Background|ProcessID" form 99999
select a.sid,b.pid,a.program cprogram,a.process,b.program
sprogram,b.spid
from v$session a,v$process b
where a.paddr(+)=b.addr
and b.addr not in(
select paddr
from v$bgprocess)
and b.addr not in(
select paddr
from v$dispatcher)
and b.addr not in(
select paddr
from v$shared_server)
and a.sid is null
and b.program <> 'PSEUDO'
/

regards
Srivenu