Re: ORA-01632 Error on Index

A copy of this was sent to Gary Brumfield <g.brumfield_at_lmco.com> (if that email address didn't require changing) On Thu, 23 Mar 2000 09:13:32 -0700, you wrote:

>
>During a period of large inserts, updates, and deletes to a single
>table, we received an ORA-01632 error for the single index that exists
>on this table. The documentation for this error states the cause as:
>The maximum amount of space allowed for saving undo entries has been
>reached for the named index. I don't understand how this could happen
>if we are issuing a COMMIT after each insert, update, or delete. Also,
>the tablespace that holds this index is sized well above the space
>needed to hold this index. Where are the index undo entries stored?
>Isn't all undo information stored in the Rollback Segment? Our Rollback
>
>Segment appears to be sized correctly. Has anyone seen this error or do
>
>you have any information to add?
>
>Thanks in advance.

ops$tkyte_at_dev8i> !oerr ora 1632
01632, 00000, "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.

You index was created with MAXEXTENTS of "x" and your index is bigger then that. Either

• increase the initial/next extent of the index
• increase the maxextents

it doesn't have anything to do with undo entries.

--
http://osi.oracle.com/~tkyte/  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Thu Mar 23 2000 - 12:11:24 CST