This content has been marked as final. Show 7 replies
It is an interesting question how Oracle manages the undo for read-only.
I might look at :
ORA-1555 Using Automatic Undo Management - How to troubleshoot [ID 389554.1]
ORA-01555 "Snapshot too old" - Detailed Explanation [ID 40689.1]
It is possible
ORA-01555 Snapshot too old
using target database control file instead of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of list command at 02/24/2011 14:24:42 ORA-01555: snapshot too old: rollback segment number 20 with name "_SYSSMU20_328 6862503$" too small RMAN-06031: could not translate database keyword
ORA-01555: snapshot too old
h3. Would forget the why and fix the issue
increase size of UNDOTBS1
Edited by: mseberg on Nov 9, 2012 7:21 AM
Perhaps, but I think that this question deals with 1) the database itself, and 2) RMAN.
My point in mentioning consistency is to highlight that I was trying to exclude even that as a possible cause. Even though no DML is changing data (readonly tablespace) I am EXPLICITLY telling the db I don't care about that either...