Re: MAX # EXTENTS ERROR MESSAGE

Stephen M. Earl wrote:
>
> I'm attempting to write a procedure to import/convert some legacy data into
> an Oracle table. I've been getting the following error message when I run
> the procedure:
>
> ERROR at line 1:
> ORA-01631: max # extents (50) reached in table HR.PER_PEOPLE_F
> ORA-06512: at "ITI.CONVERT_EMPLOYEES", line 11
> ORA-06512: at line 1
>
 

> I'm not really sure what extents in a database or tablespace do exactly so
> that may be part of my problem. If anyone has any ideas as to why this
> error is popping up I'd really appreciate some help. Also, the procedure
> does work... it imports/converts 900 out of approximately 2800 records.
>

This problem has nothing whatsoever to do with the SQL code in the procedure.

Your table was created with storage parameters too small for the amount of data you are putting in it. You need to drop and recreate the table so that all of the data will fit into one (preferably) or a few extents. Extents are just a group of blocks allocated to an object like a table. You could just modify the max_extents value for that table and bump it from 50 to 99 or whatever the max is for your OS, but having that many extents is not recommended if it can be avoided.

Read the STORAGE clause in the manual. There are many values to be set like pctfree and pctused. Do your homework and then if you have specific questions we can probably help you more.

-- 
---
Allen Kirby			AT&T ITS Production Services
akirby_at_att.com			Alpharetta, GA.