Full UNDO Tablespace In 10gR2 and above
(Doc ID 413732.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 22.214.171.124 [Release 10.2 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 30-Jun-2010
Checked for relevance on 31-Jan-2012
In a 10gR2 database with an UNDO tablespace created in NO AUTOEXTEND mode, having transactions running in the database, apparently the UNDO tablespace appears to be full.
Also many UNEXPIRED undo segments can be seen when selecting from dba_undo_extents view, although no ORA-1555 or ORA-30036 errors are reported.
Starting with 10gR2, the max retention was introduced.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document