Return-Path: <oracle-l-bounce@freelists.org>
X-Original-To: oracle-l@orafaq.com
Delivered-To: oracle-l@orafaq.com
Received: from puck1183.startdedicated.com (localhost [127.0.0.1])
 by puck1183.startdedicated.com (Postfix) with ESMTP id C1657196100F
 for <oracle-l@orafaq.com>; Thu,  3 Mar 2016 20:25:16 +0100 (CET)
Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180])
 by puck1183.startdedicated.com (Postfix) with ESMTPS
 for <oracle-l@orafaq.com>; Thu,  3 Mar 2016 20:25:16 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C1C5534491;
 Thu,  3 Mar 2016 14:25:15 -0500 (EST)
X-Virus-Scanned: Debian amavisd-new at turing.freelists.org
Received: from turing.freelists.org ([127.0.0.1])
 by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0gncJ-fN2tbe; Thu,  3 Mar 2016 14:25:15 -0500 (EST)
Received: from turing.freelists.org (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2C397343A4;
 Thu,  3 Mar 2016 14:24:35 -0500 (EST)
Received: with ECARTIS (v1.0.0; list oracle-l); Thu, 03 Mar 2016 14:23:54 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2EA1730E5B
 for <oracle-l@freelists.org>; Thu,  3 Mar 2016 14:23:54 -0500 (EST)
Received: from turing.freelists.org ([127.0.0.1])
 by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 7D+r6D2xzyYq for <oracle-l@freelists.org>;
 Thu,  3 Mar 2016 14:23:54 -0500 (EST)
Received: from hobvmisav07.pubnet.metro (metmail3.nashville.gov [170.190.30.103])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id E2FE330C84
 for <oracle-l@freelists.org>; Thu,  3 Mar 2016 14:23:53 -0500 (EST)
Received: from hobvmisav07.pubnet.metro (unknown [127.0.0.1])
 by IMSVA (Postfix) with ESMTP id DCC5F37D550
 for <oracle-l@freelists.org>; Thu,  3 Mar 2016 13:23:49 -0600 (CST)
Received: from HOBSVISHC05.nashville.org (unknown [170.190.14.6])
 by hobvmisav07.pubnet.metro (Postfix) with ESMTPS id C733437D548
 for <oracle-l@freelists.org>; Thu,  3 Mar 2016 13:23:49 -0600 (CST)
Received: from DCSOSVMS02.dcso.org (170.190.82.163) by
 HOBSVISHC05.nashville.org (170.190.14.6) with Microsoft SMTP Server (TLS) id
 14.2.318.4; Thu, 3 Mar 2016 13:23:49 -0600
Received: from DCSOSVMS02.dcso.org ([169.254.1.166]) by DCSOSVMS02.dcso.org
 ([169.254.1.205]) with mapi id 14.02.0247.003; Thu, 3 Mar 2016 13:23:49 -0600
From: "Storey, Robert (DCSO)" <RStorey@DCSO.nashville.org>
To: Oracle L <oracle-l@freelists.org>
Subject: Raid settings
Thread-Topic: Raid settings
Date: Thu, 3 Mar 2016 19:23:48 +0000
Message-ID: <FE4C2B093843BB4B873D754E5E0BE4DB01998DD98A@DCSOSVMS02.dcso.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.106.120.53]
Content-Type: multipart/alternative;
 boundary="_000_FE4C2B093843BB4B873D754E5E0BE4DB01998DD98ADCSOSVMS02dcs_"
MIME-Version: 1.0
X-TM-AS-Product-Ver: IMSVA-8.2.0.1762-8.0.0.1202-22170.002
X-TM-AS-Result: No--14.948-4.5-31-10
X-imss-scan-details: No--14.948-4.5-31-10
X-TMASE-Version: IMSVA-8.2.0.1762-8.0.1202-22170.002
X-TMASE-Result: 10--14.947500-5.000000
X-TMASE-MatchedRID: z/Aeb4Zcb6GE9zgVMk3pXmA/V00XWjDtjcUdKJrkZs3p8uhIPWDidUQS
 KPF3muIgg2TvV253YN4+Jck2RObbKkdb73gUDwkXQr2qXCJMSV/qvccKLF+4pxziuLhElX/VJZ4
 4eKUvRYc/makG0+v97gFk6w4YcqmhSOWjYlTyoLGYcl4BgqVyk3G1ZiUO5FClj2iyfwmt0k9o4t
 OBMzo2OO+6vWQCjRtKlET/T7VXa5sOVaHFOAhc6tsfxZpQv2qMtPGelsKOu4ijnkp/HAlLXORqQ
 AxbWD9+4vM1YF6AJbZO+3uGNcav97bmZosI/5ZysjvNV98mpPN5b2u/tIfC8kSvOZrR8wsz5ReV
 xxB8pl94pYZRz2cC0G23Xq3JoZ07TqmUtwuC8IFXdMh93xgwYOmNNXLo5CrKRVEQ9kpbYpw=
X-archive-position: 63764
X-ecartis-version: Ecartis v1.0.0
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
X-original-sender: RStorey@DCSO.nashville.org
Precedence: normal
Reply-To: RStorey@DCSO.nashville.org
List-help: <mailto:ecartis@freelists.org?Subject=help>
List-unsubscribe: <oracle-l-request@freelists.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: oracle-l <oracle-l.freelists.org>
X-List-ID: oracle-l <oracle-l.freelists.org>
List-subscribe: <oracle-l-request@freelists.org?Subject=subscribe>
List-owner: <mailto:mark.bobak@proquest.com>
List-post: <mailto:oracle-l@freelists.org>
List-archive: <http://www.freelists.org/archives/oracle-l>
X-list: oracle-l
--_000_FE4C2B093843BB4B873D754E5E0BE4DB01998DD98ADCSOSVMS02dcs_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

When configuring raids, what seems to be the consensus on doing Read Ahead?=
  By normal practice I always ask for the raid holding the database to be W=
rite Through, but I've never really looked at the Read Ahead.

Any thoughts or good/bad reasons for setting this on/off?

Just curious.

--_000_FE4C2B093843BB4B873D754E5E0BE4DB01998DD98ADCSOSVMS02dcs_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">When configuring raids, what seems to be the consens=
us on doing Read Ahead?&nbsp; By normal practice I always ask for the raid =
holding the database to be Write Through, but I&#8217;ve never really looke=
d at the Read Ahead.&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any thoughts or good/bad reasons for setting this on=
/off?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Just curious.<o:p></o:p></p>
</div>
</body>
</html>

--_000_FE4C2B093843BB4B873D754E5E0BE4DB01998DD98ADCSOSVMS02dcs_--

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


