This content has been marked as final. Show 8 replies
Probably undersized UNDO tablespace?
the global size is good .... 5 Gb. .
Only one user was working on the database at this time.
Looks like a bug.
Can you try increasing the OPTIMAL parameter for the SYSTEM rollback
segment? Typically the SYSTEM rollback segment is created much
the "public" rollback segments..
1 select segment_name,
5* from dba_rollback_segs
SEGMENT_NAME INITIAL_EXTENT NEXT_EXTENT STATUS
------------------------------ -------------- ----------- ------
SYSTEM 57344 57344 ONLINE
RBS0 524288 524288 ONLINE
RBS1 524288 524288 ONLINE
RBS2 524288 524288 ONLINE
RBS3 524288 524288 ONLINE
RBS4 524288 524288 ONLINE
RBS5 524288 524288 ONLINE
RBS6 524288 524288 ONLINE
alter rollback segment system storage(optimal 'X'M)
All the above said things can only be done when u running in manual undo management mode. as it is above quoted it is running auto undo management mode
Thanks you're right !
I'm running on automatic mode for undo ... I think that satishkandi didn't see it.
Another idea ?
Thanks in advance
I think "kccrga" has replied to "senthil007" and not my post. The things that "Senthil007" has mentioned in his post (changing Optimal settings) can be done only in Manual undo mode.
But the fact that even if you have auto undo management, undersized undo tablespace (not big enough to hold the undo information for all the transactions on the system at a given point in time) will need wrapping in the undo segments leading to above error. Probably your transactions are generating too much undo information.
thanks for these posts.
How to estimate the most finely possible a good sizing for undo tablespace ?