http://www.lifeaftercoffee.com/2006/08/31/raid-5-and-oracle-databases/ because I don't believe in life before coffee... Wed, 23 Nov 2011 03:01:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.lifeaftercoffee.com/2006/08/31/raid-5-and-oracle-databases/comment-page-1/#comment-5112 Zach Mon, 11 Sep 2006 01:52:26 +0000 http://www.lifeaftercoffee.com/2006/08/30/raid-5-and-oracle-databases/#comment-5112 Oracle is now using Apple XServes for internal use: http://www.apple.com/itpro/profiles/oracle/ based on the grounds of cheap and reliable. Oracle is now using Apple XServes for internal use: http://www.apple.com/itpro/profiles/oracle/ based on the grounds of cheap and reliable.

]]> http://www.lifeaftercoffee.com/2006/08/31/raid-5-and-oracle-databases/comment-page-1/#comment-4989 spiralbound.net » Why Modern RAID 5 is Ideal for Oracle Databases Fri, 08 Sep 2006 18:42:16 +0000 http://www.lifeaftercoffee.com/2006/08/30/raid-5-and-oracle-databases/#comment-4989 [...] There is a convention of thought amongst Oracle DBA’s that databases should never be installed on disks that are configured into a RAID 5 array. The argument goes, that since Oracle accesses and writes to random points within relatively large files, the overhead of constantly calculating block-level parity on these files is substantial, resulting in serious performance degradation. They suggest that RAID 1 (mirroring) is the ideal disk configuration since no parity needs to be calculated, and Oracle is more than happy to divide up its database over many smaller mount points. [...] [...] There is a convention of thought amongst Oracle DBA’s that databases should never be installed on disks that are configured into a RAID 5 array. The argument goes, that since Oracle accesses and writes to random points within relatively large files, the overhead of constantly calculating block-level parity on these files is substantial, resulting in serious performance degradation. They suggest that RAID 1 (mirroring) is the ideal disk configuration since no parity needs to be calculated, and Oracle is more than happy to divide up its database over many smaller mount points. [...]

]]>