- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Max extents reached
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 06:11 PM
тАО08-14-2003 06:11 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 06:46 PM
тАО08-14-2003 06:46 PM
Re: Max extents reached
If the Prodution table reached maxextent frequently. To avoid I suggest reorging the table and calculated the size in mb that will be inserted into the table for the next 6months so that it can be allocated as the initial extent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 08:59 PM
тАО08-14-2003 08:59 PM
Re: Max extents reached
There are some problems in increasing the maximum number of extents for all the segments in my database, not too sure the reason. Are there any other ways to solve this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2003 09:17 PM
тАО08-14-2003 09:17 PM
Re: Max extents reached
You did not mention the version of Oracle Database you are using!
You should be using Dictionary managed tablespaces!
If you get the error "max extents", you need to alter the max extents for the table. If you have to do this on a given table over and over -- you need to rethink your extent size for that table. It might need to be larger.
In order to analyze if that problem would be solved by altering max extents -- you need only look at the error message. A good DBA might be proactive and run a query every now and then like:
select owner, segment_name, segment_type, extents, max_extents
from dba_segments
where max_extents-extents <= 3;
that'll tell you the objects that are getting near to failing.
If you get the "unable to extend" due to lack of space -- you need to increase the size of your datafile or add more datafiles.
I use maxextents unlimited typically with FIXED size extents (pctincrease = 0, initial = next for all objects in a tablespace and all objects use the same initial and next values).
See
http://technet.oracle.com/doc/oracle8i_816/server.816/a76965/c02block.htm#2775
for details on extent management.
If you have Oracle 8i, you should start using LOCALLY MANAGED tablespaces (LMT) with system managed extent sizes (UNLIMITED).
A locally managed tablespace with uniform extents makes that the "de-facto" rule, you cannot subvert it as you can with a dictionary managed tablespace.
- LMT totally avoids fragmentation -- it is impossible to have fragmentation in these tablespaces.
- LMT are much faster at allocating and de-allocating extents - many order of magnitudes faster.
- LMT decrease contention on the data dictionary.
hope this helps!
regards
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 01:23 AM
тАО08-15-2003 01:23 AM
Re: Max extents reached
But if you can go for LMT.
see this thread
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb3fb5dc05a7ad711abdc0090277a778c,00.html
Rgds,
Jean-Luc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 02:05 AM
тАО08-15-2003 02:05 AM
Re: Max extents reached
The Oracle version is 7.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 02:24 AM
тАО08-15-2003 02:24 AM
Re: Max extents reached
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 08:31 AM
тАО08-15-2003 08:31 AM
Solutionin 7.2 the maximum value of maxextens was related to the db_block_size.
With 2K it has been 121 with 4K it was 249 and with 8K it had been 505.
Once you bounced that one, no other way out than to reorganize the segment. So be sure to adjust NEXT in a corresponding way and be sure to have enough spare place to adjust.
You should upgrade at least to 7.3.3 which will give you the ability to use a higher maximum on max-extents.
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 06:27 PM
тАО08-15-2003 06:27 PM
Re: Max extents reached
select * from dba_segments where owner not like 'SYS%' and next_extent < (1024*500);
This will show you any objects with under 500k extent sizes.
2. Check your dba_tablespaces view. The default initial and next extent sizes define what sizes to use on objects without a set initial/next size. Increasing these to something like 1m for each can help keep new objects allocating a large number of extents on accident.
hope this helps,
Thanks,
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2003 04:26 PM
тАО08-17-2003 04:26 PM
Re: Max extents reached
I think you answered part of my question (I can't increase the max extents). I guess I have a 7.2 database with block size 2K which will have a max extent limits of 121.