<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic EVA Disk Group Performance in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/eva-disk-group-performance/m-p/4741607#M43385</link>
    <description>Hello, Oracle best practices  recommended  to implement a disk group for each Oracle database engine. how can it affect if I have two or more engines in the same diskgroup?&lt;BR /&gt;&lt;BR /&gt;Oracle 10.2.0 RHEL 5.4&lt;BR /&gt;EVA 8400&lt;BR /&gt;thank you very much.</description>
    <pubDate>Thu, 20 Jan 2011 16:58:10 GMT</pubDate>
    <dc:creator>sube-it</dc:creator>
    <dc:date>2011-01-20T16:58:10Z</dc:date>
    <item>
      <title>EVA Disk Group Performance</title>
      <link>https://community.hpe.com/t5/operating-system-linux/eva-disk-group-performance/m-p/4741607#M43385</link>
      <description>Hello, Oracle best practices  recommended  to implement a disk group for each Oracle database engine. how can it affect if I have two or more engines in the same diskgroup?&lt;BR /&gt;&lt;BR /&gt;Oracle 10.2.0 RHEL 5.4&lt;BR /&gt;EVA 8400&lt;BR /&gt;thank you very much.</description>
      <pubDate>Thu, 20 Jan 2011 16:58:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/eva-disk-group-performance/m-p/4741607#M43385</guid>
      <dc:creator>sube-it</dc:creator>
      <dc:date>2011-01-20T16:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Group Performance</title>
      <link>https://community.hpe.com/t5/operating-system-linux/eva-disk-group-performance/m-p/4741608#M43386</link>
      <description>The EVA8400 is a fairly "good" and fast array. I do not know where you got that best practice from but what it probably meant was to have a separate DG for your "hot" Oracle "files" -- i.e. archive log, redo log, etc.&lt;BR /&gt;&lt;BR /&gt;DG1 will be likely for your main DataFiles for howevr many Oracle Instance you wish to stash there&lt;BR /&gt;&lt;BR /&gt;DG2 will likely be for your archive logs, redos, etc.&lt;BR /&gt;&lt;BR /&gt;Note however the rules: disk members should be in multiples of 8 and the larger the disk count, the higher performaning will be your Vdisks (more spindles engaged)&lt;BR /&gt;&lt;BR /&gt;We however sticked with one very large (240 Disks) Diskgroup -- with about a dozen large Databases on 'em (ASM). WHat we do as added best practice is to have multiple large Vdisks (we've settled for 200 to 400 GB sized Vdisks) so the DB instance can load balance / stripe accross the controllers.&lt;BR /&gt;&lt;BR /&gt;HTH...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Jan 2011 17:43:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/eva-disk-group-performance/m-p/4741608#M43386</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-01-21T17:43:01Z</dc:date>
    </item>
  </channel>
</rss>

