The Oracle docs note this on the ora-01552 error:
Action: Create one or more private/public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. If the non-system tablespace has AUTO segment space management, then create an undo tablespace.
On Oracle DBA Forums , user Chris_Pena encountered ORA-01552 while using this SQL statement:
SQL> select segment_name, status from dba_rollback_segs;
SEGMENT_NAME STATUS
------------------------------ ----------------
SYSTEM ONLINE
_SYSSMU1$ OFFLINE
_SYSSMU2$ OFFLINE
_SYSSMU3$ OFFLINE
_SYSSMU4$ OFFLINE
_SYSSMU5$ OFFLINE
_SYSSMU6$ OFFLINE
_SYSSMU7$ OFFLINE
_SYSSMU8$ OFFLINE
_SYSSMU9$ OFFLINE
_SYSSMU10$ OFFLINE
As a response, Burleson reminded the user that you cannot force a SQL in system RBS. Because of this, to avoid ORA-01552 he should have created public rollback segments, and resolved the current issue by trying to undo (depending on the release in use).
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/12285417/viewspace-586813/ ,如需转载,请注明出处,否则将追究法律责任。