Re: ksuosstats global area

From: Dion Cho <>
Date: Wed, 10 Nov 2010 10:13:47 +0900
Message-ID: <>

Hi, Joel.

That would mean that it isn't waiting for the shared latch acquisition, but it did wait for a short time. After that short waiting, the session is busy doing something thus burning CPU. V$SESSION_WAIT.STATE would show 'WAITED SHORT TIME' or 'WAITED UNKNOWN TIME' if my assumption servers it right.

You can try PROCESSSTATE dump and/or CALLSTACK dump to find out what the session is really doing.

Dion Cho - Oracle Performance Storyteller (english) (korean) (tpack)

On Wed, Nov 10, 2010 at 4:08 AM, <> wrote:

> I’ve been using DBOptimizer and using Tanel Poders scripts.
> SID 0 is using a lot of CPU (in a particular test case). If the latch was
> named ‘shared pool latch’ I’d have an explanation, but LatchProfX is
> revealing that latch ‘ksuosstats global area’ is at the top and ‘shared pool
> latch’ is not listed.
> I went to MOS and searched, as well as Google, and ksuosstats normally
> shows up as part of a list of latches and the discussion is normally
> centered around another issue.
> Can anyone let me know what this might be all about? Is it part of the
> shared pool, and therefore part of the initialization process normally
> associated with SID 0? (thanks Tanel).
> Joel Patterson
> Database Administrator
> 904 727-2546

Received on Tue Nov 09 2010 - 19:13:47 CST

Original text of this message