Starting in Oracle9i, rollback segments are re-named undo logs.
Traditionally transaction undo information was stored in Rollback Segments until a commit or rollback statement was issued, at which point it was made available for overlaying.In Oracle9i, manual undo management is still available in addition, but most Oracle professionals choose the new automatic method which frees DBAs from routine undo management tasks and tuning.Best of all, automatic undo management allows the DBA to specify how long undo information should be retained after commit, preventing "snapshot too old" errors on long running queries.This is done by setting the undo_retention parameter. The default is 900 seconds (5 minutes), and you can set this parameter to guarantee that Oracle keeps undo logs for extended periods of time.Rather than having to define and manage rollback segments, you can simply define an Undo tablespace and let Oracle9i take care of the rest.Turning on automatic undo management is easy. All you need to do is create an undo tablespace and set undo_management=auto and bounce your database:
As you can see there is a undo_retention that you can set to avoid the 1555. Try that to see if it work. Here is how to see and set it.
Â
SQL> show parameter undo_retention
Â
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_retention integer 9000
SQL> alter system set undo_retention=10800;