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 







ORA-25141: invalid EXTENT MANAGEMENT clause tips

Expert Oracle Database Tips by Donald BurlesonDecember 27, 2015

Question: I am getting an ORA-25141: invalide EXTENT MANAGMENT clause error when trying to create the system tablespace's extent management dictionary using the following:

create database
group 1 ('/u01/app/oradata/anand/redo1a.log') size 100M,
group 2 ('/u01/app/oradata/anand/redo2a.log') size 100M,
group 3 ('/u01/app/oradata/anand/redo3a.log') size 100M
datafile '/u01/app/oradata/anand/system.dbf' size 400M extent management
sysaux datafile '/u01/app/oradata/anand/sysaux.dbf' size 300M default temporary tablespace temp tempfile '/u01/app/oradata/anand/temp.dbf' size 50M

 Running this code results in the ORA-25141: invalid EXTENT MANAGEMENT clause.  How can I create the system tablespace's extent management directory without getting the ORA-25141?

Answer:  The oerr information on the ORA-25141 says the following:

ORA-25141: invalid EXTENT MANAGEMENT clause

Cause: An invalid option appears for EXTENT MANAGEMENT clause

Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE

FYI, nobody uses dictionary managed tablespaces much anymore, they can cause bottlenecks in the data dictionary as tablespaces grow! Instead, check out locally managed tablespace (LMT).

There are some working examples of the CREATE DATABASE command HERE.

Further review of the documentation reveals the following points on the use of extent_management_clause for creating a locally managed SYSTEM tablespace.  Omitting this clause will result in the SYSTEM tablespace being dictionary managed.

 Caution: A locally managed SYSTEM tablespace cannot be changed to be dictionary managed, nor can you create any other dictionary-managed tablespaces in this database.

  • If this clause is specified, the database must have a default temporary tablespace, because a locally managed SYSTEM tablespace cannot store temporary segments.
  • If EXTENT MANAGEMENT LOCAL is specified but you do not specify the DATAFILE clause, the default_temp_tablespace clause can be omitted. Oracle Database will create a default temporary tablespace called TEMP with one datafile of size 10M with autoextend disabled.
  • If both EXTENT MANAGEMENT LOCAL and the DATAFILE clause are specified, then the default_temp_tablespace clause must be used and datafile explicitly specified for that tablespace.

If the instance has been opened in automatic undo mode, similar requirements exist for the database undo tablespace:

  • If EXTENT MANAGEMENT LOCAL is specified but  the DATAFILE clause is not, the undo_tablespace clause can be omitted. Oracle Database will create an undo tablespace named SYS_UNDOTBS.
  • If both EXTENT MANAGEMENT LOCAL and the DATAFILE clause are specified, then the undo_tablespace clause must be used and a datafile for that tablespace explicitly specified.
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 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster