RE: RE: Locally Managed Tablespaces

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Fri, 21 Mar 2003 18:20:09 -0800
Message-Id: <24738.322762@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_01C2F019.8F9524C0
Content-Type: text/plain;

charset="iso-8859-1"

Well, my first suggestion would be to buy a software package from a reputable software company that lets you predict object growth and an estimate of when your tablespace will be full. Contact me for more details. :)

But seriously, you can write a report that shows the number of extents and the amount of freespace in each tablespace, and review the report periodically (say once a week). Which is what I did back in my production DBA days. I imagine you could have a database procedure that checks the free space in a tablespace and sends you an e-mail, or even pages you if you have e-mail forwarded to a pager.
Setting the datafiles to autoextend just pushes the problem back to the OS level - how do you know when your disks will be full?

> -----Original Message-----
> From: Ryan [mailto:rgaffuri_at_cox.net]
> 
> so for normal business you should not use autoextend? You 
> should monitor it
> yourself? What are some tips for monitoring the database to 
> see if you need
> to extend your tablespace manually? Do you use DBMS_ALERT and 
> read the v$
> views and then broadcast a message if you need to extend a tablespace?

------_=_NextPart_001_01C2F019.8F9524C0
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>

Well, my first suggestion would be to buy a software =
package from a reputable software company that lets you predict object = growth and an estimate of when your tablespace will be full. Contact me = for more details. :)

But seriously, you can write a report that shows the =
number of extents and the amount of freespace in each tablespace, and = review the report periodically (say once a week). Which is what I did = back in my production DBA days. I imagine you could have a database = procedure that checks the free space in a tablespace and sends you an = e-mail, or even pages you if you have e-mail forwarded to a = pager.

Setting the datafiles to autoextend just pushes the =
problem back to the OS level - how do you know when your disks will be = full?

> -----Original Message-----
 > From: Ryan [<A =
HREF=3D"mailto:rgaffuri_at_cox.net">mailto:rgaffuri_at_cox.net</A>]
 > 
 > so for normal business you should not use =
autoextend? You 
 > should monitor it
 > yourself? What are some tips for monitoring the =

database to </FONT>

 > see if you need
 > to extend your tablespace manually? Do you use =
DBMS_ALERT and 
 > read the v$
 > views and then broadcast a message if you need =
to extend a tablespace? Received on Fri Mar 21 2003 - 20:20:09 CST