ORA-1628 Max # Extents Reached Using AUM On Locally Managed Tablespace
(Doc ID 761176.1)
Last updated on FEBRUARY 27, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]Information in this document applies to any platform.
Symptoms
Getting ORA-1628 errors for undo segments using Automatic Undo Management, AUM,
on undo locally managed tablespace.
o Alert log shows many ORA-1628 errors:
ORA-1628: max # extents 32765 reached for rollback segment _SYSSMU184$
ORA-1628: max # extents 32765 reached for rollback segment _SYSSMU184$
ORA-1628: max # extents 32765 reached for rollback segment _SYSSMU184$
or/and
ORA-00600: internal error code, arguments: [4355], [1628], [0], [166], [0], [121], [], []
ORA-00604: error occurred at recursive SQL level 3
ORA-1628: max # extents (32765) reached for rollback segment _SYSSMU184$
Call stack trace is similar to:
ksedst ksedmp ksfdmp kgeriv kgesiv ksesic5
ktsauu kqrpsf ausdrvo ausdrvs ausdrv opiexe
opiosq0 opipls opiodr rpidrus skgmstack rpidru
rpiswu2 rpidrv psddr0 psdnal pevm_EXIM pfrinstr_EXIM
pfrrun_no_tool pfrrun plsql_run peicnt kkxexe opiexe
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |