Thanks for the tip Matt. There has been some discussion on the possibility of having a script that runs periodically and does a tcpdump. Sounds like this is the way to go - subject to testing in non- prod env of course! On 16 Aug 2012, at 03:04, Matthew Zito wrote: > You could do this with tcpdump/snoop/whatever packet sniffing > technology you want, and then load it into wireshark. That should be > sufficient to see the latency times packet-wise. > > Not as clean or elegant as a v$ table or iostat, but you can get the > data. > > Matt > > On Wed, Aug 15, 2012 at 4:51 PM, Austin Hackett <hacketta_57@xxxxxx> > wrote: >> Hi Dana >> This info doesn't exactly relate to ASM, but I hopefully it'll be of >> use to you in the future... >> >> I've recently started a new role at shop that uses Linux, Direct NFS >> and NetApp (no ASM) and as others have suggested, the solution does >> have a number of nice management features. >> >> However, I am finding the apparent lack of read and write latency >> stats frustrating. >> -- //www.freelists.org/webpage/oracle-l