↪ replying to Jeff Larsen
Jeff Larsen wrote:
> Is there any way to determine which user session
> might be causing oninit to hog the CPU? Can any
> of the onstat -g commands help?
Examine syssesprof for sessions with "excessive" activity (bufreads,
lockreqs, isreads). If possible, initialize stats (onstat -z) prior to
the check to make it easier.
e.g select sid, lockreqs, bufreads, isreads, seqscans, total_sorts
from syssesprof
where bufreads > 1000 -- assuming you've just "onstat
-z"ed
order by 3 desc
run a few times would flush out the "hot" sessions.
Rudy