Re: Possible causes of ORA-01630: max extents reached.

From: Brett Neumeier <random_at_nospam.com>
Date: 15 Apr 1998 20:19:56 GMT
Message-ID: <6h34pc$lgb$1@eve.enteract.com>

tmcconechy_at_bcbc.bc.ca wrote:
> When running a report in our production system which used to
> work fine. The client recieves the ORA-01630: max extents
> (249) reached in temp segment in tablespace TEMP.

You probably have a relatively small blocksize (2K? 4K?) and therefore there can be only 249 extents in any given segment.

The report generated a temporary segment which needed to be larger than 249 extents, so it bombed.

The way to fix it is to change the default storage parameters of the TEMP tablespace. For example, if the initial and next extent in TEMP is 1MB, with PCTINCREASE 0, you could change it to initial and next of 5MB; then your 249 extents would translate to a much larger segment.

-bn
(the domain is really "enteract") Received on Wed Apr 15 1998 - 15:19:56 CDT