Re: ORA-01631 problem

From: Joel Garry <joelga_at_pebble.ml.org>
Date: 1998/01/05
Message-ID: <68ralc$vvo$1@pebble.ml.org>#1/1

In article <68munr$a1t$1_at_scream.auckland.ac.nz>,
Alan MCCulloch <amccullo_at_ccu1.auckland.ac.nz> wrote:

>"Bong Khin Fah" <bongkf_at_pc.jaring.my> writes:
>
>>hi everybody,
>
>
>>how would you normally deal with
>>ORA-01631 max # of extents 'num' reached in table 'name' error ?
 

>>the current maxextents of tablespace = 121, pctincrease = 0.
 

>>thank you
 

>>Bong Khin Fah
>>Sarawak Information Systems Sdn. Bhd.
>
>Other respondents mentioned exporting and re-creating with appropriate
>parameters....personally I have never had any trouble with the easier
>option, of increasing max extents a little bit, and increasing
>the size of the next extent parameter. I have waited for an opportune
>time to do the export and import - e.g. a major Database version upgrade,
>when two birds can be killed with one stone.

maxentents is based on blocksize, so many default installations cannot go beyond 121.

>
>Alan McCulloch
>Senior Programmer
>Clinical Trials Research Unit
>Dept of Medicine
>Auckland University
>

-- 
These opinions are my own and not necessarily those of Information Quest
jgarry@eiq.com                           http://www.informationquest.com
http://ourworld.compuserve.com/homepages/joel_garry
"See your DBA?"  I AM the @#%*& DBA!

Received on Mon Jan 05 1998 - 00:00:00 CST