Actually, SYSTEM is one of the only tablespaces I like to have it set on.
While I originally set it to autoextend when I was doing an upgrade I left
it active on the grounds that while I know how to recover if by some chance
one of my datafiles runs out of space, I'm uncertain as to the
I've been running with autoextend on (though limited to 2Gig) and never had
a problem.
-Original Message-
Sent: Thursday, October 24, 2002 5:26 PM
To: Multiple recipients of list ORACLE-L
I run my SYSTEM tablesaces in autoextend, and have for some time. I run them
that way from the
FWIW I'd go with Dennis here. I don't like AUTOEXTEND on the SYSTEM
tablespace.
(In fact I'm not overenamoured of AUTOEXTEND on any datfile, except maybe on
dev and sandbox databases).
If the SYSTEM tablespace isn't used for rollbacks (apart from the SYSTEM
rollback) or temporary segments and the
I use AUTOEXTEND and it has been extremely helpful to me in managing growth.
However, my policy is not to use autoextend for SYSTEM, rollback tablespace,
or temp tablespace.
SYSTEM (for me) is relatively stable. The only time I have significant growth
in SYSTEM is during an upgrade. For
Title: RE: System Tablespace and Autoextend
I have read complaints about SYS.IDL% objects having PCTINCREASE 50 and
space problems when they extend, in the forums. I went to check and
mine are already set to 0 along with 2147483645 MAXEXTENTS. I created
a TAR and verified with Oracle
Sam -
I haven't made the system tablespace autoextend because I can't easily
recover the space if it overextends. I would rather take the risk that
something hits an error from a lack of space in the system tablespace. With
other tablespaces you can always rebuild the tablespace if you need
Sam,
Autoextend caused tablespace corruption for me once, but it was over 5
years ago with Personal Oracle 7.3.2.3 on Win95 - not the most reliable OS
that Oracle has ever ported to. ;-)
We have several 8.1.7 databases here, on both Win2k and HPUX. Autoextend,
even on System, has caused no
Hello Sam
I do not know specifically about SYSTEM tablespace but from a bitter
experience beware of the 4GB limit. if a datafile on NT/2000 autoextend
beyond a multiple of 4GB (8,12...) then that datafile is GONE. We had a
production database crashing on this problem and had to call in Oracle
I run my SYSTEM tablesaces in autoextend, and have for some time. I run them
that way from the point of database creation and have never had a problem.
There were some problems with autoextend in earlier versions of 8 (and I
think they managed to migrate to early 8i versions as well) with 2GB
