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

 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
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

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

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







When Oracle Storage Parameters are Ignored

Oracle Database Tips by Burleson Consulting

October 29, 2015

Question:  I understand that there are Oracle storage features that cause the standard table and index storage options to be ignored.  Under what conditions are the storage parameters ignored?

Answer (by Chris Aiken):  Oracle uses various parameters to define how data blocks are handled within the database.  These storage parameters are all explained below, giving a brief overview of what they do and how they operate, as well as when the parameter is handled differently by Oracle. 

It is important to note that with Automated Segment Space Management enabled, and in some cases with Locally Managed Tablespaces, certain parameters are disregarded.  These storage parameters are PCTFREE, PCTUSED, MINIMUM EXTENT, MAXEXTENTS, INITIAL, NEXT, PCTINCREASE, FREELIST GROUPS and FREELISTS. 

When PCTFREE is ignored

PCTFREE is a block storage parameter which specifies the amount of free space Oracle should leave in a database block for future updates.

PCTFREE is NOT ignored with ASSM is used (segment space management auto).  The PCTFREE is also not ignored when Locally-managed tablespaces (LMT) are used.

Oracle will continue adding new rows to the block until the remaining space is equal to the PCTFREE parameter. The default value for the PCTFREE parameter is PCTFREE=10. Any value between 0 and 99 may be used as long as the sum of PCTFREE and PCTUSED is not greater than 100.

When talking about PCTFREE, it must be noted that indexes are a special case. PCTFREE may be specified for an index, but only when the index is initially created.

 The PCTFREE parameter is only used when an index is created.  After index creation, new index block entries are made and PCTFREE is ignored.

When PCTUSED is ignored

PCTUSED is a storage parameter in Oracle which specifies when a database block is empty enough for Oracle to add it to the free list. When the percentage of used space in a block is greater than the PCTUSED parameter, Oracle will not add new rows to the block. The default settings for all Oracle tables are PCTUSED=40.

  • PCTUSED is disregarded for all objects created in locally managed tablespaces when Automated Segment Space Management (ASSM) is enabled.

  • PCTUSED is ignored for indexes:  Oracle must manage the freelist re-link process for index tree management because the index node boundaries are the same as the index data block size.  Hence, PCTUSED is not used for index segments.

When MINEXTENTS is ignored

In a dictionary-managed tablespace, the MINEXTENTS parameter defines the total number of extents to be allocated when a segment is created. MINIMUM EXTENT is used for locally managed tablespaces, but only to compute the initial amount of space to be allocated.

When MAXEXTENTS is ignored

MAXEXTENTS, for dictionary-managed tablespaces, is the maximum number of extents that can ever be allocated for the segment.

Locally Managed Tablespaces ignores MAXEXTENTS.  Because Oracle manages the extents under a locally managed tablespace, MAXEXTENTS will be ignored.

When INITIAL is ignored

The INITIAL parameter defines the size of the first extent of an object. The default value for this is the size of 5 data blocks. In a dictionary-managed tablespace, if the MINIMUM EXTENT parameter was set at the time the tablespace was created, then Oracle rounds the value of INITIAL up to the specified MINIMUM EXTENT size, but only if necessary.

In a locally managed tablespace, Oracle uses the value of INITIAL together with the size of extents specified for the tablespace to calculate the size of the first extent of the object. It must also be noted that INITIAL cannot be set by using an ALTER TABLE statement.

When NEXT is ignored

NEXT represents, for dictionary-managed tablespaces, the size of the next incremental extent to be allocated for a segment. The default value for NEXT is always the size of 5 data blocks. The default value for the second extent is always equal to the original setting for NEXT. For each new extent, the NEXT is set to the previous size of NEXT multiplied by (1 + PCTINCREASE/100). If you manually set the value of the NEXT parameter, the next allocated extent will have the specified size regardless of the size of the most recently allocated extent and the PCTINCREASE parameter.

NEXT is ignored with LMT (locally managed tablespaces) because the database automatically manages extents.

When PCTINCREASE is ignored

PCTINCREASE is the storage parameter, for dictionary-managed tablespaces, which specifies the percentage by which each incremental extent grows over the previous extent allocated for a segment.

Just like the NEXT parameter, PCTINCREASE is not valid for locally managed tablespaces so it is ignored.


The FREELIST GROUPS parameter specifies the number of groups of free lists for the database object you are creating. The default, and minimum, is 1 which causes all free lists of a segment to be available to all instances.

  • The FREELISTS and FREELIST GROUPS are disregarded for objects created in locally managed tablespaces (LMT).

  • The FREELISTS and FREELIST GROUPS parameter is disregarded  with segment space management AUTO (bitmapped freelists, a.k.a. ASSM.).

The FREELISTS parameter specifies the number of free lists available for each of the free list groups for the object. This parameter is not used for tablespaces. The default and minimum value for FREELISTS is 1, and the maximum value depends on block size. Attempting to specify FREELISTS to a value greater than allowed will generate an error message informing you of the maximum value.

Get the Complete
Oracle SQL Tuning Information 

The landmark book "Advanced Oracle SQL Tuning  The Definitive Reference"  is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.



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 -  2016

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.


Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster