Troubleshooting / Documentos / Soporte Técnico / Servicios / Tilsor
 
 

ORA-1628, ORA-1630, ORA-1631, ORA-1632 MAXEXTENTS REACHED


Creation Date: 09-JAN-1997
Last Revision Date: 11-JUL-2000


Problem Description:
====================

You are working with the database and you have encountered one of the
following errors:

ORA-1628 max # extents (%s) reached for rollback segment %s
// *Cause: Tried to extend rollback segment already at maxexents value
// *Action: If maxextents storage parameter less than system allowable max,
// raise this value. Consider upping the pctincrease value as well.

ORA-1630 max # extents (%s) reached in temp segment in tablespace %s
// *Cause: A temp segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
// maximum, you can raise that. Otherwise, raise pctincrease for the
// tablespace

ORA-1631 max # extents (%s) reached in table %s.%s
// *Cause: A table tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params

ORA-1632 max # extents (%s) reached in index %s.%s
// *Cause: An index tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.

The max extents error occurs when the current number of extents equals the
maximum number of extents in the max_extents parameter for the object or the
maximum number of extents allowable for the db_block_size , whichever is smaller,
and an attempt is made to add another extent. Max extents can be set for an object
using the MAXEXTENTS option of the storage clause.

Search Words
============
ORA-01638 ORA-01630 ORA-01631 ORA-01632