RE: Dbms_refresh and archived logs

From: <Stephen.Lee_at_DTAG.Com>
Date: Tue, 2 Mar 2004 09:38:15 -0600
Message-ID: <D6339830FC73944E889CC3CEADDB205B0790921A@bu-dtagpo1.tracs.com>

Actually, this might not be such a bad idea. Our databases that get all of their data by replication (and we're talking lots and lots of replication) are run in noarchivelog mode. We run a rows=n export daily and keep the scripts used to create the database. In this case, we can rebuild the database from sources other than a hot backup. It is not as convenient has being able to tell rman to restore database, recover database, but we can do it. The systems on which these run get hammered very hard and anything to lighten the load was needed.

If this is not acceptable in your case, one way to reduce the number of archived logs is to increase the size of the redo logs (snort snort). Have you tried using /dev/null as your archived log destination?

> -----Original Message-----
>
> Is there a way to prevent dbms_refresh from generating redo
> log entries?
> One job generates 170+ archived logs every morning.
>
> The tablespace, tables are all set to nologging but makes no
> difference.
>
> I logged a TAR but so far the response I got was: how about
> setting your
> database in noarchivelog mode. LOL
>

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.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Tue Mar 02 2004 - 09:35:39 CST