Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: RE: Locally Managed Tablespaces

RE: RE: Locally Managed Tablespaces

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Fri, 21 Mar 2003 10:59:38 -0800
Message-Id: <24738.322731@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_01C2EFDC.054CFB90
Content-Type: text/plain;

        charset="iso-8859-1"

> -----Original Message-----
> From: rgaffuri_at_cox.net [mailto:rgaffuri_at_cox.net]
> 
> thanks in case I happen to work on a 7.3 database....
> 
> what kind of pctincrease should I set? What about the other 
> settings? Just curious. 

The current thinking is that uniform extents are a good thing. So in 7.3, try and "manually" enforce uniform extents: initial = next for all clusters/tables/indexes in the same tablespace pctincrease=0 for all objects
These should of course be the settings for the DEFAULT STORAGE clause on the create tablespace. Then to create a cluster/table/index you can (should?) use tablespace defaults and skip the storage parameter on the CREATE cluster/table/index statement.

My personal opinion: always use maxextents unlimited but put your object in a tablespace where the values of INITIAL and NEXT will prevent the object from having more than 1000 extents.

Autoextend datafiles: my personal opinion is don't use those, because you should have an idea of how and when your database is going to grow, and if you need more space it's nice to be aware of it. Of course this means the risk of failure when a datafile is full, but the same thing can happen with autoextend when the disk gets full.

------_=_NextPart_001_01C2EFDC.054CFB90
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.2654.45">
<TITLE>RE: RE: Locally Managed Tablespaces</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: rgaffuri_at_cox.net [<A =
HREF=3D"mailto:rgaffuri_at_cox.net">mailto:rgaffuri_at_cox.net</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; thanks in case I happen to work on a 7.3 =

database....</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; what kind of pctincrease should I set? What =
about the other </FONT>
<BR><FONT SIZE=3D2>&gt; settings? Just curious. </FONT>
</P>

<P><FONT SIZE=3D2>The current thinking is that uniform extents are a =
good thing.</FONT>
<BR><FONT SIZE=3D2>So in 7.3, try and &quot;manually&quot; enforce =
uniform extents:</FONT>
<BR><FONT SIZE=3D2>initial =3D next for all clusters/tables/indexes in =
the same tablespace</FONT>
<BR><FONT SIZE=3D2>pctincrease=3D0 for all objects</FONT>
<BR><FONT SIZE=3D2>These should of course be the settings for the =
DEFAULT STORAGE clause on the create tablespace. Then to create a = cluster/table/index you can (should?) use tablespace defaults and skip = the storage parameter on the CREATE cluster/table/index = statement.</FONT></P>

<P><FONT SIZE=3D2>My personal opinion: always use maxextents unlimited =
but put your object in a tablespace where the values of INITIAL and = NEXT will prevent the object from having more than 1000 = extents.</FONT></P>

<P><FONT SIZE=3D2>Autoextend datafiles: my personal opinion is don't =
use those, because you should have an idea of how and when your = database is going to grow, and if you need more space it's nice to be = aware of it. Of course this means the risk of failure when a datafile = is full, but the same thing can happen with autoextend when the disk = Received on Fri Mar 21 2003 - 12:59:38 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US