Re: Monitoring questionable long running sessions

"VC" <boston103_at_hotmail.com> wrote:

>Posting execution plans as I asked earlier would be useful too.

It would not help. It turned out that the sessions were really "broken". I compiled a statspack report for the time between Friday evening and Monday morning. The pertinent SQL query did not even show up in the report! (Although they were consuming CPU time almost alone).

After killing the DB sessions... nothing happened. "Something" was still running 100% on two CPUs. I had to kill the OS processes to get rid of the CPU hug.

I read something about mad "spinning" CPU.

The case was reported to Oracle, we will see what they say.

>select * from v$session_wait
>where sid in (coordinator_sid, slave_sids);

What I am missing is something like a "pstree" for DB sessions, in other words, how can I find slave_sids belonging to one coordinator? I will have to examinate the v$session view, perhaps there is a field indicating "I am a slave_sid".

Sofar, the only way to identify broken sessions is via all these peculiarities.

Bye
Rick Denoire Received on Mon Jul 12 2004 - 14:58:55 CDT