Rollback Segment: Read Consistency Errors

Dear all,

Quoting from a book:
"Troubleshooting Rollback Segment Problems: Read Consistency Errors:
Recall that rollback segments allow transaction-level read consistency for all statements running on the database. A long-running query in one session that starts before a change on that data is committed by another session will see the data as it existed pre-commit. If Oracle cannot provide a read-consistent view of data, the following error will ensue:

ORA-01555 - snapshot too old (rollback segment too small)

The solution to the problem is to re-create the rollback segments with a higher minimum number of extents, larger extents, or a higher optimal rollback segment size. You cannot simply increase maxextents to resolve this problem."

If the maxextents is bigger, the max rollback segment size is bigger, so it takes longer to get this snapshot too old error. Does my rationale hold? Thanks in advance.

Dino Received on Sat Aug 11 2001 - 23:52:14 CDT