>-----Original Message-----
>From: Sanjay Kumar [mailto:[EMAIL PROTECTED]]
>Sent: jeudi, 8. mars 2001 11:01
>
>I have a table which consists of Long Raw column in addition to other columns of Number and Varchar2 datatypes.
>
>I have the datafile size set to 2GB. The average length of the messages
>goes up to 100M, sometimes more than that.
>
>I have now added three datafiles to that tablespace each greater
>than the first datafile. But I still keep getting the
>ORA-01631 Max extents reached for table "A" error.
>
>What do I do resolve this error?
>
>I am using 8K as the DB block size on SOlaris with Oracle 816
>It is not a prod environment instead a dev environment.
Check the max_extents for the table:
select extents, max_extents
from dba_segments
where owner = 'table_owner_name' and segment_name = 'table_name'
and segment_type = 'TABLE' ;
You will have to change the max_extents on the table with the SQL command alter table, e.g.
alter table owner.name storage (maxextents new_value) ;
But before you do so, you may want to ask yourself - is there a reason that the current "maxextents" value was chosen? Should some rows from the table be archived deleted? Of course, since this is a development environment perhaps it's not as important to know the answers to those questions.
------
any ignorant comments made are the sole responsibility of J. R. Kilchoer and should not reflect adversely upon my employer.
Jacques R. Kilchoer
(949) 754-8816
Quest Software, Inc.
8001 Irvine Center Drive
Irvine, California 92618
U.S.A.
http://www.quest.com
