RE: I/O EVENTS

Hi Greg,

> Maybe not one, but what about two? At the same time v$system_event is
> checked a couple of times, so you can see a time slice,
> v$sysstat can be
> checked, focusing on CPU used by this session, parse time cpu
> and recursive
> cpu usage. One view gives wait time, one gives CPU time.

There is a lot to be said about using V$SYSSTAT too. The point is that the CHR is derived out of V$SYSSTAT and hence one needs to be careful. Also, some of the values in V$SYSSTAT have meaning only in V$SESSTAT.... A lot can be deduced from sesstat, and the real interesting ones such as V$ROWCACHE haven't been explored to their fullest depths yet. I think the point I was trying to get across was that V$SYSTEM_EVENT is a good place to start, not neccessarily the only view....

John Kanagaraj

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: John Kanagaraj
  INET: john.kanagaraj_at_hds.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).