Re: Error during insert records to table...

I'm not an Oracle DBA, but I play one on TV so I'll take a stab at this question. On recent versions of Oracle (I know this holds true for version 7.3.3 at our office), it is possible to set MAXEXTENTS to a really large number. But if you need to do this, the other storage parameters of the table might need to be examined. A table split into many extents pays a performance penalty because the data may be spread all over the disk rather than in contiguous blocks. It is more advisable to create the table with fewer, larger extents. Depending on the amount of fragmentation in the tablespace, this may or may not be possible.

MAXEXTENTS is there to set an upper bound on the size of the table. Without it, it would be possible for an errant process to insert rows into a table until the table filled the entire tablespace, possibly causing great weeping and gnashing of teeth for other objects in the tablespace.

David wrote:
>
> Hello Patrick,
>
> I want to ask, is it possible to set the maxextents to some very large
> value? (e.g. 10000) Is there any disadvantage to set maxextents to very large
> value? Or any limit to set the value of maxextents? And what is the use of
> MAXEXTENT parameter in creating the table?
>
> David
>
> Patrick Hamou wrote:
>
> > Hi !,
> >
> > Well the problem is quite simple, youve reached the Maxextent value for your
> > table (witch is by the way
> > the default maxextents value for Oracle 7)
> > To solve the problem, you have to recreate the table with larger Extents and
> > (or) set the Nomaxextent
> > parameter for your table if you have Oracle 8...
> >
> > regards,
> >
> > Patrick Hamou,
> > Oracle DBA
> > patrickhamou_at_hotmail.com
> >
> > David <david_petit_at_yahoo.com> wrote in message
> > news:3811FF38.C8866C79_at_yahoo.com...
> > > Hello all,,
> > >
> > > When I insert rows to the table, I got the following error message:
> > >
> > > ERROR at line 1:
> > > ORA-01631: max # extents (121) reached in table USER.TESTING
> > >
> > > Could anyone tell me why such an error message shown and how to
> > > solve this problem?
> > >
> > > THanks,
> > > David
> > >
Received on Mon Oct 25 1999 - 02:15:55 CDT