increasing extents because of ORA-01632

[Lod]

I have a question concerning the extents from a database.
The database stops occasionaly with an ORA-01632 error. Increasing the
max_extent from the individual index, named in the error is keeping
things going, but there should be a way solving this in a more
structural manner. There is plenty of (table)space on the system. When
I query dba_tablespaces for our tablespace it gives a
next_extent=40969 and a max_extent=2048 and a pct_increase=0. I
increased the pct_increase to 50. Does this give the indexes more room
to live or should I (also) increase the the next_extent.
The database is running on a Compaq Alpha -Tru64- server.

[Daniel Roy]

Also,
if you're running at least Oracle 8i, consider locally-managed
tablespaces. With those, you don't need to worry anymore about number
of extents, pctincrease, ...

Daniel

I pct_increase = 50, then the first next _extend will be 40969, and the
following will be 61454, then the next 81938 and so on...

notes that max_extend may take the value UNLIMITED.