Re: DBMS_REFRESH and Redo-Logging

From: Eric Buddelmeijer <>
Date: Mon, 16 Feb 2009 13:17:11 +0100
Message-ID: <>


You can reduce the amount of redo generation considerably by dropping any indexes before the refresh and recreate them (nologging) after the refresh. If you have any indexes on the MV at all and have not already done this.

Kind regards,

2009/2/16 <>

> Hi folks,
> i've got a mv created with nologging-clause on 10204. This view
> is regularly refreshed *completly *using dbms_refresh.refresh. During the
> refresh a plenty of archive-logs are generated, flooding our
> archive-destination.
> As result oracle deactivates the full destionation forcing the database to
> halt.
> Error:
> ARCH: Archival stopped, error occurred. Will continue retrying
> ORACLE Instance dada - Archival Error
> ORA-16014: log 1 sequence# 49531 not archived, no available destinations
> After that the archiver is pausing for 2 or 3 minutes.
> As i know that there is no way to prevent redo-log generation, do you know
> a workaround for such a scenario? Expect increasing file-systemspace and
> deactivating archivelog mode. :-)
> And secondly: how am i able to prevent oracle from waiting for the
> archiver. Is there any way to reenable the deacitvated
> archive_destionations?
> regards, jan

Received on Mon Feb 16 2009 - 06:17:11 CST

Original text of this message