This is a discussion on EXP Issue within the Oracle Database forums, part of the Database Server Software category; --> I'm receiving an: EXP-00056: ORACLE error 1555 encountered ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I'm receiving an: EXP-00056: ORACLE error 1555 encountered ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" too small The exp continues after this message and at the end of the 3 hour exp I get the following message: "Export terminated successfully with warnings." Will this exp be ok or is it corrupt based on the 1555 error? I read some where that setting the UNDO_RETENTION period higher solves this issue, it's currently set to 600, should I up it? The UNDOTBS1 is sized at 22G and when I view the usage during the exp it does not appear to be filling up. The exp cmd settings are : BUFFER=128000 FULL=Y COMPRESS=N STATISTICS=NONE FILESIZE=2G Thx in Advance |
| ||||
| al1 wrote: > I'm receiving an: > > EXP-00056: ORACLE error 1555 encountered > ORA-01555: snapshot too old: rollback segment number 2 with name > "_SYSSMU2$" too small > > The exp continues after this message and at the end of the 3 hour exp I > get the following message: > "Export terminated successfully with warnings." > > Will this exp be ok or is it corrupt based on the 1555 error? > > I read some where that setting the UNDO_RETENTION period higher solves > this issue, it's currently set to 600, should I up it? > The UNDOTBS1 is sized at 22G and when I view the usage during the exp > it does not appear to be filling up. > > The exp cmd settings are : > BUFFER=128000 > FULL=Y > COMPRESS=N > STATISTICS=NONE > FILESIZE=2G > > Thx in Advance Yes, it will be corrupt - the error prevented the affected table to be fully fetched, so the export misses some data. Yes, you should increase the UNDO_RETENTION so that it at least exceeds the time it takes to export the largest table. You may want to check V$UNDOSTAT.MAXQUERYLEN, which should hint you how long the longest query was running in the past week. Undo retention should be at least that long. Hth, Vladimir M. Zakharychev N-Networks, makers of Dynamic PSP(tm) http://www.dynamicpsp.com |