RE: Optimal Distribution of Datafiles

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Fri, 26 Jan 2001 12:42:57 -0800
Message-Id: <10753.127650@fatcity.com>

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------_=_NextPart_001_01C087D8.9098E9C0
Content-Type: text/plain;

charset="iso-8859-1"

> -----Original Message-----
> From: Pablo ksksksk [mailto:p_rodri99_at_yahoo.es]
> Sent: vendredi, 26. janvier 2001 10:56
>
> Why do you place SYSTEM in a dedicated disk?
>etc...

Just for comparison purposes, here's what the "Oacle8 DBA Handbook" (author: Kevin Loney, OraclePress) suggests for the "9-disk solution" and the "7-disk compromise" (chapter 4: Physical database layouts, p. 99)

9-disk

1      Oracle Software
2      SYSTEM tablespace, Control file 1
3      RBS tablespace, RBS_2 tablespace, Control file 2
4      DATA tablespace, Control file 3
5      INDEXES tablespace
6      TEMP tablespace, TEMP_USER tablespace, DATA_2 tablespace
7      TOOLS tablespace, INDEXES_2 tablespace
8      Online Redo logs 1, 2 and 3, Export dump file destination disk
9      Application software, Archived redo log destination disk

7-Disk
1      Oracle Software
2      SYSTEM, TOOLS, INDEXES_2 tablespaces, Control file 1
3      RBS, RBS_2 tablespaces, Control file 2
4      DATA tablespace, Control file 3
5      INDEXES, TEMP, TEMP_USER, DATA_2 tablespaces
6      Online Redo Logs 1, 2 and 3, Export dump file destination disk
7      Application software, Archived redo log destination disk

legend:
DATA = standard-operation tables, DATA_2 = static tables used during standard operation, INDEXES = indexes for the standard-operation tables, INDEXES_2 = indexes for the static tables, RBS = standard-operation rollback segments, RBS_2 = specialty rollback segments used for data loads, TEMP_USER = temporary segments created by a particular user, TOOLS = RDBMS tools tables

The book recommends to calculate I/O 'weights' for the datafiles. If you estimate, he suggests the following: If the most active tablespace has an I/O 'weight' of 100, use 35 as a 'weight' for SYSTEM and for indexes use 1/3 of the weight of the associated tablespace.

any ignorant comments made are the sole responsibility of J. R. Kilchoer and should not reflect adversely upon my employer.

Jacques R. Kilchoer
(949) 754-8816
Quest Software, Inc.
8001 Irvine Center Drive
Irvine, California 92618
U.S.A.
http://www.quest.com

------_=_NextPart_001_01C087D8.9098E9C0
Content-Type: text/html;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =

charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2652.35">

<TITLE>RE: Optimal Distribution of Datafiles</TITLE>
</HEAD>
<BODY>

> -----Original Message----- > From: Pablo ksksksk [<A = HREF=3D"mailto:p_rodri99_at_yahoo.es">mailto:p_rodri99_at_yahoo.es</A>]=

<BR><FONT SIZE=3D2>&gt; Sent: vendredi, 26. janvier 2001 10:56</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Why do you place SYSTEM in a dedicated =

disk?

<BR><FONT SIZE=3D2>&gt;etc...</FONT>
</P>
<BR>

Just for comparison purposes, here's what the = "Oacle8 DBA Handbook" (author: Kevin Loney, OraclePress) = suggests for the "9-disk solution" and the "7-disk = compromise" (chapter 4: Physical database layouts, p. = 99)

9-disk
 1      Oracle = Software
 2      SYSTEM tablespace, = Control file 1
 3      RBS tablespace, = RBS_2 tablespace, Control file 2
 4      DATA tablespace, = Control file 3
 5      INDEXES = tablespace
 6      TEMP tablespace, = TEMP_USER tablespace, DATA_2 tablespace 7      TOOLS tablespace, = INDEXES_2 tablespace
 8      Online Redo logs 1, = 2 and 3, Export dump file destination disk 9      Application = software, Archived redo log destination disk

7-Disk
 1      Oracle = Software
 2      SYSTEM, TOOLS, = INDEXES_2 tablespaces, Control file 1 3      RBS, RBS_2 = tablespaces, Control file 2
 4      DATA tablespace, = Control file 3
 5      INDEXES, TEMP, = TEMP_USER, DATA_2 tablespaces
 6      Online Redo Logs 1, = 2 and 3, Export dump file destination disk 7      Application = software, Archived redo log destination disk

legend:
 DATA =3D standard-operation tables, DATA_2 =3D = static tables used during standard operation, INDEXES =3D indexes for = the standard-operation tables, INDEXES_2 =3D indexes for the static = tables, RBS =3D standard-operation rollback segments, RBS_2 =3D = specialty rollback segments used for data loads, TEMP_USER =3D = temporary segments created by a particular user, TOOLS =3D RDBMS tools = tables

The book recommends to calculate I/O 'weights' for = the datafiles. If you estimate, he suggests the following: If the most = active tablespace has an I/O 'weight' of 100, use 35 as a 'weight' for = SYSTEM and for indexes use 1/3 of the weight of the associated = tablespace.

------
 any ignorant comments made are the sole = responsibility of J. R. Kilchoer and should not reflect adversely upon = my employer.

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Jacques R. Kilchoer</FONT>
<BR><FONT SIZE=3D2>(949) 754-8816</FONT>
<BR><FONT SIZE=3D2>Quest Software, Inc.</FONT>
<BR><FONT SIZE=3D2>8001 Irvine Center Drive</FONT>
<BR><FONT SIZE=3D2>Irvine, California 92618</FONT>
<BR><FONT SIZE=3D2>U.S.A.</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.quest.com" =

Received on Fri Jan 26 2001 - 14:42:57 CST