RE: diagnosing physical IO issues beyond the database

From: Matthew Zito <mzito_at_gridapp.com>
Date: Tue, 28 Jul 2009 13:06:20 -0400
Message-ID: <C0A5E31718FC064A91E9FD7BE2F081B101D4B9D6_at_exchange.gridapp.com>


Yes, service times are one of the strongest indicators that the array itself is bogged down, or slow. It won't help oyu in the situation where only particular blocks of data on a device are slow for some reason, but it will let you see that individual volumes are having trouble keeping up with the load.

Matt

-----Original Message-----

From: oracle-l-bounce_at_freelists.org on behalf of Allen, Brandon Sent: Tue 7/28/2009 12:02 PM
To: oracledbaquestions_at_gmail.com; oracle-l_at_freelists.org Subject: RE: diagnosing physical IO issues beyond the database  

Use sar and/or iostat to see for yourself what the disk service and wait times look like from the OS perspective while you're running the problematic table scans, then if they're high ask your OS admin and SAN admin to explain why.  

Regards,

Brandon  


Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--

http://www.freelists.org/webpage/oracle-l Received on Tue Jul 28 2009 - 12:06:20 CDT

Original text of this message