Oracle process

[Rushank]

Hello,

Is there a way to find out stale orcale process or runaway oracle process?? Basically I want to know which oracle process is eating up the resource

Thanks in advance
Rush.

[James R. Ferguson]

Hi:

# top

# ps -ef|grep oracle

Regards!

...JRF...

[Rushank]

I need to know about stale process..

[Sridhar Bhaskarla]

Rushank,

It's difficult to find a runaway process unless you know about the processes and how they behave. There is nothing like a ps -ef|grep runaway and find the processes.

One way is to use the XPG4 ps with pcpu output and get the processes that have been constantly consuming CPU and then verify whether those processes really needed to be running and then killing them if not. Examples are oracle connections.

UNIX95= ps -e -o "pcpu args" |sort -n |tail -10

gives top ten processes with high cpu utilization. Then you can verify each process and kill the ones that are runaway.

-Sri

[Rushank]

I usually check with this command

UNIX95= ps -e -o ruser,vsz,pid,args | sort -rnk2 | more

This gives me number of oracle process that are running but I am not able to make out which one is *NOT* required..

[harry d brown jr]

If you don't already have a license for glance, install the trial version.

live free or die

[Frank Slootweg]

I hardly know anything about Oracle, but *perhaps* the *PID numbers in the ipcs(1) output can tell you which PIDs *are* used (look at the *TIME values) and hence, by elimination, indicate which PIDs are not used.

However be *very* carefull and do not terminate a process unless you are absolutely sure that it is indeed 'left-over'.

[Roger Baptiste]

<< This gives me number of oracle process that are running but I am not able to make out which one is *NOT* required..>>

->One way to track is to
run TOP utility and see
which process is *constantly*
on the top five list of processes. Then, do a
ps on those pids to see
how soon their CPU usage time
changes. A process which
takes cpu time rapidly without
seeming to do anything is
a big suspect. You notice
this usually with broken
client connections or
Xwindown emulators run from
the PC, but not closed properly, or broken sql scripts.

To track the process further, take the pid and
check in glance , what
exactly it is doing (system
calls, wait states).

Finally, check with the
owner of the process, before
killing it. There is always
a probability that it is
a valid process.


-raj