The most likely solution is to increase the size and/or
number of rollback segments to avoid the ORA-1555. Also,
if your rollback segments are not equally sized, consider
that likelyhood of encountering ORA-1555 is directly=20
dependent on the size of the SMALLEST rollback segment,
not the largest one.

I have a materialized view in a data warehouse.
On the hour, the view is refreshed from production.
The refresh fails on occasion due to ora-1555(snapshot too old), that
occurs in the prod db or source across db links.
I would like to use set transcation and use a large RBS.
How can I accomplish this when the view and refresh exists in one db, =
but
the db generating the 1555 is across db links and would not benefit from
set transaction as the local rb segments are not the issue.
Hmmmm?
Thanks
--=20

..
David

Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--

FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html---------------------------------------------------------------------------------------------------------------------------------
To unsubscribe send an email to: oracle-l-request_at_freelists.org
and put 'unsubscribe' in the subject line.