Solution : https://service.sap.com/sap/support/notes/185822 (SAP Service marketplace login required)
Summary :
This SAP note addresses the ORA-01555 "snapshot too old" error that arises in settings using either traditional rollback segments or Oracle's Automatic Undo Management (AUM). The note outlines three main causes of this error: 1) delayed block cleanout, 2) insufficient size of rollback segments or undo tablespaces, and 3) overwritten rollback information required by running SELECT statements. Remedies include adjusting database parameters to minimize uncommitted block cleanouts, right-sizing rollback and undo segment parameters, and ensuring frequent enough commitments during large transactions. Using AUM is strongly recommended to decrease the likelihood of ORA-01555 errors.
Key words :
time --> sqlplus sap<sid>/<passwd> sql> select, rollback segment sql> select initial_extent, sydba'sql> select hwmsize, overwriting specific statements decreases, long running batch job, evenly distributes transactions evenly, classic rollback segment configuration, traditional rollback segment layout, sql> select trunc, job run longer
Related Notes :
1539473 | LCC optimization - General questions/answers (FAQ) |
1137317 | ROIRA_ARC_WRITE (SSR archiving write), ORA-1555 dump |
1074030 | R3trans: "Duplicate key" composite SAP note (as of Rel 6.10) |
955702 | ORA-1555 error while running TDMS |
789390 | Material forecast: Error ORA-01555 for background forecast |
600141 | Oracle9i: Automatic UNDO Management |
383823 | MP38: Restriction according to materials |
365421 | ORA-00600 [1113] when generating statistics |
96296 | CC-ERROR: Database problem in client copy |
88656 | R3trans: Duplicate key composite SAP note (Release 4.0-4.6) |
67205 | CC-INFO: Copying large and productive clients |
3807 | Error messages regarding rollback and undo segments |