Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Possible causes of ORA-01630: max extents reached.
Reaching the maxextents is not a wierd error, but there may be underlying
flwas in the tablespace design, like not sizing the tablespaces / datafiles
properly.
You may want to set the NEXT (extent) parameter in the STORAGE clause for the
TEMPORARY tablespace to a higher value. When you do this change, make sure you
increase the size of the datafile for the TEMP tablespace or add one more
datafiles to the tablespace. Looks like you have some high activity which make
use of a lot of TEMP segments (order by, create index etc). If this type of
activity is happenning beacuse of a special operation (like creating index for
a large table), then you may want to drop the new datafile after the operation
is complete. If the operations are normal, you may want to leave the
additional datafiles and look into the other tuning aspects (like increasing
the SORT_AREA_SIZE).
Good luck,
CM
-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Fri Apr 17 1998 - 18:22:11 CDT
![]() |
![]() |