Re: ORA-01631 problem

From: Frédéric Trébuchet <frederic.trebuchet_at_sncf.fr>
Date: 1997/12/22
Message-ID: <01bd0ee0$b7a6d870$5a02a994@mimp46>#1/1

Use export with compress option, drop your table and re-import your datas. Table will be created with appropriate storage clause. For future, you have to estimate (or to compute) the size of your objects (tables and indexes) and create them with a good storage clause to avoid multiples extents which is a cause of poor performances.

TRF Bong Khin Fah <bongkf_at_pc.jaring.my> a écrit dans l'article <01bd0eb0$707fd260$5a1815ac_at_ccm-pc>...
> 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.
>
>
Received on Mon Dec 22 1997 - 00:00:00 CST