Re: Getting orphan processes chewing up CPU Time

Ian Sparkes wrote:
>
> Mark Wiseman wrote:
> >
> > After a day's work there are oracle processes running when there are not
> > supposed to be. I can go in a kill them but I can't tell the difference
> > between valid processes and orphan processes. Does anyone know a way to
> > keep the orphan processes to a minimum?
> >
> > Will also entertain claims that it can't be done.it can definatly be done.
>
> The following process is MUCH easier in X-windows as you can look at both screens at once
>
> I'm assuming you are running on a Unix machine
>
> 1) Bring up Sql*Dba or Server Manger (depending on DB version)
>
> 2) Using the the "process monitor" & "ps -ef | grep ora" (or similar Unix cmd)
> compare valid oracle connections to the running server processes
>
> 3) Kill Unix server processes that are not actually connected to the database
>
> To give advice on how to keep them to a minimum I'd need more info on your configuration
> I experienced this same opportunity on a unix box. Check the parent pid
of the orphan. If it's 1 (init) blast away (kill -11 <pid>) [ NOT kill -9].
The opionions expresses are solely my own - and sometimes I even get them right. Received on Tue May 28 1996 - 00:00:00 CEST