I'm puzzled.
We had a table that hit maximum extents on our QA server (unlike production
it isn't cleaned out on a daily basis). I deleted most of the rows, leaving
only a few thousand.
The next day, when inserting more rows I hit the maxextents exceeded error
on an index on that table (of course the number of extents hadn't been
reduced but I would have thought there'd be plenty of room in 121 existing
extents after most of the rows were deleted). I rebuilt the index and it
went from 121 extents to 1 extent, resolving the problem, but leaving some
curiosity.
It's a primary key sequence based index. Any ideas?
Jay Miller
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Miller, Jay
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
