RE: Dbms_refresh and archived logs
- From: "Khedr, Waleed" <Waleed.Khedr@xxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 1 Mar 2004 20:46:41 -0500
Complete refresh uses hint --+ append
So if the MVW is defined as nologging, there should not be any redo except
for index rebuild.
Also indexes could be dropped and rebuilt after the refresh.
Only if it's complete refresh.
Regards,
Waleed
-----Original Message-----
From: Boivin, Patrice J [mailto:BoivinP@xxxxxxxxxxxxxxxxx]
Sent: Monday, March 01, 2004 10:55 AM
To: 'oracle-l@xxxxxxxxxxxxx'
Subject: Dbms_refresh and archived logs
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
Patrice.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
