Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Changing table index maxextents unlimited

Oracle Database Tips by Donald Burleson

Having a small value for maxextents for tables and indexes can cause unplanned outages and many DBA's set all objects to "maxextents unlimited", and all data files to "autoxtend on" (the default with later releases of Oracle).

There are two schools of thought on maxextents unlimited:

  • Don't risk lock-up - Tables should be free to grow ad-infinitum, and the DBA should never risk an unplanned outage by having a table reach max extents.
     

  • Lock a rapidly-growing table - A table might have an out-of-control insert, and the DBA wants to have the table lock-up.

I believe that it is an Oracle best practice to use "maxextents unlimited" and "autoextend on", thereby pushing the space management to the OS filesystem level.  You can easily manage the filesystems with Linux/Windows monitoring and alert whenever an object is taking too-frequent extents.

If you accidentally create objects with a small integer value for maxextents and you want to use "maxextents unlimited", you can use the following dictionary script to change all tables and indexes to alter then to "maxextents unlimited":

spool runme.sql
 
select
   'alter '||
   object_type||
   ' '||
   object_name||
   ' storage (maxextents unlimited);'
from
   dba_objects
where
   object_type in ('TABLE','INDEX')
and owner = 'XXX';
spool off
 
@runme

For a permanent fix for maxextents unlimited, change the tablespace default for new objects to maxextents unlimited (viewed in the dba_tablespaces max_extents column):

alter tablespace
   ts_32k
storage (maxextents unlimited);


 


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational