RE: Auto Extend On, Increment By

Yes I agree, (mostly), I should have said that I would autoextend TEMP and UNDO but limit the growth with max size set. The other datafiles however I am still unconvinced in my case that they need maxsizes. All I would do is increase the maxsize or add another data file anyway when they filled up. We do not do massive loads (presently). I agree we (all) should monitor.  

As to the main question however, is deciding on a good increment_by size. I think I received enough input on this, even though most input was on philosophy :-), including one who responded privately lambasting me for not knowing that 'next extents' where the same as 'increment[al]'. Oh well.  

My conclusion for the moment is to set them to 10Mbs, (Small, but actually some are smaller yet). Then monitor using Grid the rate of growth, and make adjustment accordingly, mostly up, (64 - 100Mb, except System). The Peoplesoft applications will be put on hold for now as they have quite a few tablespaces and many of the do not grow at all, so they will be looked at later separately.  

Now, I just have to hone in on where in the EM Grid this is done. (Available space is already monitored). Where I can monitor rate of growth of all datafile(s) growth.  

Thanks for the comments.

Joel Patterson
Database Administrator
joel.patterson_at_crowley.com
x72546
904 727-2546

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Allen, Brandon Sent: Friday, March 16, 2007 11:44 AM
To: Smith.Steven_at_DOL.GOV; Oracle-L_at_freelists.org Subject: RE: Auto Extend On, Increment By  

This is what I do:

• Autoextend on
• Next size should be something moderate to prevent frequent space allocation penalties, but not too large to the point where it would cause a very significant space allocation penalty (e.g. 1+ minutes) for the unfortunate user that adds a row and requires another extent. I usually go with something around 64MB, but it's all relative and there is obviously no "right" answer to this one
• Maxsize should pretty much always be set with autoextend to prevent the tablespaces from growing out of control and filling up the filesystem
• Monitoring should still be in place - autoextend should not be a replacement for monitoring, it should just be used to prevent the mundane maintenance of adding space to tablespaces and getting calls in the middle of the night when some rare event occurs that requires more space than your normal growth trend predicted.

Regards,

Brandon  

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

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