Re: Possible causes of ORA-01630: max extents reached.

From: joseph Li <lijoecyn_at_netspace.net.au>
Date: 16 Apr 1998 12:59:22 GMT
Message-ID: <6h4vba$gj1$4@otis.netspace.net.au>

Your DB_BLOCK_SIZE is probably 4096 hence the default maximum number of extents is 249. I think in Oracle 7.2 onwards you can increase that maximum by 'Alter tablespace TEMP storage ( maxextents 1000 )', the 1000 is just a guide. Maybe you INITIAL and NEXT extent for TEMP is small and the report has more data to handle => more data to sort. You can increase the size of the NEXT extent before re-run of the reporting job.

Regards
Joe

In article <6h333d$kjo$1_at_nnrp1.dejanews.com>, tmcconechy_at_bcbc.bc.ca says:
>
>When running a report in our production system which used to work fine.
>The client recieves the ORA-01630: max extents (249) reached in temp segment
>in tablespace TEMP.
>
>There are many extents and over 500 megs of space left for the system.
>
>What could possibly be causing my problem.
>
>Thanks for any advise!
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Thu Apr 16 1998 - 07:59:22 CDT