Be careful about your use. Use it by alll means. But do be careful. If
you set autoextend on without limits to prevent extension beyond the
available disk for file extension, you can wind up with a permanently
corrupted tablespace. You would then have to do a offline drop on the
datafile containing imaginary physical block addresses, and possibly
even have to restore the table(s) from export. Don't let autoextend
overrun available physical space!
Connor McDonald wrote:
>
> Frank Calfo wrote:
> >
> > Is autoextend a good feature to turn on or is it better to leave it off and
> > add datafiles manually as needed?
> >
> > Is there any performance advantage in using or not using autoextend?
>
> As with most Oracle features - Autoextend can be very handy when used
> *sensibly*...
>
> Examples of good use: Having autoextend on TEMP tablespaces and
> ROLLBACK tablespaces so that people "never" get sorting errors or
> rollback errors...since you can also shrink these tspace's back to a
> nominal size if required.
>
> Examples of bad use: Turning it on everywhere since not enough planning
> was done to work out just how big things were going to get...
>
> HTH
Received on Thu Sep 30 1999 - 21:28:01 CDT
