RE: issues with oracle partitioning and SAN striping

Ryan,  

    I used both in a previous position, there were no problems, nor hot spots. Remember that most SAN solutions have a RAM buffer cache which does 99% of your read activity. The particular application I was working on did continuous writes to the partitions during the course of the day & continuous reads as well. Performance was extremely good especially since a lot of the data was used by "customer" facing applications like a gatekeeper, CIM application, & shipping panel. These apps did not appreciate anything being slow, especially the gatekeeper & CIM apps. Imagine what would be said if a robot paused for a few seconds waiting for data? Can you say instant phone call?     

Dick Goulet, Senior Oracle DBA

45 Bartlett St Marlborough, Ma 01752, USA Tel.: 508.573.1978 |Fax: 508.229.2019 | Cell:508.742.5795

RGoulet_at_kanbay.com
: POWERING TRANSFORMATION  

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of ryan_gaffuri_at_comcast.net
Sent: Monday, November 06, 2006 10:01 AM To: oracle-l_at_freelists.org
Subject: issues with oracle partitioning and SAN striping

Someone on our team raised concerns about using both oracle table level partitioning and SAN striping. As I have said before I am more on the developer side of things. Has anyone had problems with this?  

"SAN striping of data file and Oracle partitions) techniques we are using will sure collide with each other creating worse performance than using either one of the two. Since SAN is not aware of how oracle is handling the partitions, data from two hash or range partitions can end up on the same spindle thereby making it serial I/O."    

--
http://www.freelists.org/webpage/oracle-l