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-30036: unable to extend segment by string in undo tablespace "string"   tips

Oracle Error Tips by Burleson Consulting


Oracle docs note this about ORA-30036:

ORA-30036: unable to extend segment by string in undo tablespace "string"

Cause: the specified undo tablespace has no more space available.

Action: Add more space to the undo tablespace before retrying the operation. An alternative is to wait until active transactions to commit.

It is important to note that ORA-30036 is associated with UNDO tablespaces.  If you use autoextend on an UNDO tablespace  because you can easily run out of UNDO and receive ORA-30036 along with an aborted update. For a full note on UNDO sizing, check my notes on Oracle UNDO sizing.


I received ORA-30036 after a shutdown.  A job was killed so that we could reboot after it had been running.  We issued the shutdown command but the database didn't stop and then had shutdown abort.  Now, trying to restart we get this:

Errors in file /u0704/oracle/proddb/9.2.0/admin/PROD/udump/prod_ora_16213.trc:
ORA-30036: unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'
Error 30036 happened during db open, shutting down database
USER: terminating instance due to error 30036
Instance terminated by USER, pid = 16213
ORA-1092 signalled during: ALTER DATABASE OPEN...


The workload had been running for 12 hours  and caused a workload spike.  You received ORA-30036 as the transaction attempted to recover in startup, which caused you to met the UNDO limit.  The ORA-30036 error is thrown as the database refuses to open. 

You can resolve ORA-30036 by first mounting the database and disabling UNDO:

alter system set undo_management = manual scope=spfile;

Next, you must shutdown to resolve ORA-30036 and then startup again using rollback mode and a system rollback segment.  Use UNDO tablespace to add files and then use alter system set undo_management=auto scope=spfile; to activate the UNDO once again.  To fully resolve ORA-30036, shutdown and restart again.



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

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.


Hit Counter