Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Auto Extend On, Increment By

RE: Auto Extend On, Increment By

From: Mercadante, Thomas F \(LABOR\) <>
Date: Fri, 16 Mar 2007 08:50:48 -0400
Message-ID: <ABB9D76E187C5146AB5683F5A07336FFE08C34@EXCNYSM0A1AJ.nysemail.nyenet>


This whole discussion always is defined by your current infrastructure. In your case, you have slow steady growth, so an active auto-extend infrastructure and monitoring process probably does not make sense.  

But for those of us who have databases that either grow regularly, or have active batch loads, auto-extend and active disk growth monitoring is a requirement. I certainly do not want to be called to work because an Oracle data file is full when there is enough room on disk where it can grow by itself. Of course, once you turn this on, you need a monitoring process to forecast when you will fill disk and when you need to inform management that more disk needs to be purchased.  

So there is no right or wrong way to do this. As with all things, Oracle gives us the ability to allow the database to grow automatically. But we don't need to use it.  


This transmission may contain confidential, proprietary, or privileged information which is intended solely for use by the individual or entity to whom it is addressed. If you are not the intended recipient, you are hereby notified that any disclosure, dissemination, copying or distribution of this transmission or its attachments is strictly prohibited. In addition, unauthorized access to this transmission may violate federal or State law, including the Electronic Communications Privacy Act of 1985. If you have received this transmission in error, please notify the sender immediately by return e-mail and delete the transmission and its attachments.

[] On Behalf Of
Sent: Friday, March 16, 2007 8:08 AM
To:; Cc:
Subject: RE: Auto Extend On, Increment By  

I've done it both ways, I'd like to get GRID involved. The fact of the matter is, our databases hardly grow at all. The disk available space is monitored by two tools and the system admins also.  

It seems so much easier in this situation. We do not do loads here. My issue is mainly what difference does it really make in this situation what size the increment_by is? 1280 blocks. Sounds good, and if some extend more often... oh well... there is a small performance hit then. (OLTP). I can do bigger.  

As a sidenote, to save time. I have just installed and upgraded EM GRID database, repository, OMS and agents. However, have never depended on it or gotten familiar yet. (I am, don't send me all the links to the manuals). I have used the console. Anyway, in this case, to save time, I would like to dive straight to the monitoring portion that EM can do for me with this issue:  

Rate of growth of datafiles. Available disk space is a default. With LMT and autoextend, and limited growth, I just don't see why I have to page myself watching tablespace free space. I am by myself as a DBA, I hardly get called, but I am still 24/7, and don't need "at this point in the reorganization of the databases" to burdon myself with extra monitoring pages.  

Sorry, the situation here is not as hot as a lot of you have it, perhaps that is why there is 'resistance' :-)  


Joel Patterson
Database Administrator
904 727-2546

From: Dennis Williams [] Sent: Thursday, March 15, 2007 8:00 PM
To: Patterson, Joel
Subject: Re: Auto Extend On, Increment By  


If you decide to switch to autoextend, I think this is the least issue to decide. The important issue is how space will be monitored. Done right, autoextend can give you a single space indicator to monitor. But make sure none of your tables have a limit of extents or you'll get a failure even though you still have disk space.  

Dennis Williams

Received on Fri Mar 16 2007 - 07:50:48 CDT

Original text of this message