On 4/2/07, Hemant K Chitale <hkchital@xxxxxxxxxxxxxx> wrote:
We have this Materialized View which generates more I/O when running the initial "DELETE" portion of a COMPLETE Refresh --- the DELETE generates a lot of UNDO and, more importantly, REDO (for the UNDO !).
You could make it do a TRUNCATE instead of a DELETE. //www.freelists.org/archives/oracle-l/01-2007/msg00666.html -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist