RE: Nologging clause
Date: Wed, 1 Apr 2009 08:58:15 -0700
Message-ID: <2A8185DC02A8CE4C8413E0A26A8A831A0325A2FBDF_at_XEDAMAIL2.ex.ad3.ucdavis.edu>
Greg,
Again, thank you. The next question I have is in regards to deletes. Is it possible to do a direct path delete (does that even make sense)? As I mentioned this will be a repository for CAS tickets and they will be deleted at their expiration time. Is it possible to avoid generation of redo on a delete as well?
Thanks.
Bill Wagman
Univ. of California at Davis
IET Campus Data Center
wjwagman_at_ucdavis.edu
(530) 754-6208
-----Original Message-----
From: Greg Rahn [mailto:greg_at_structureddata.org]
Sent: Tuesday, March 31, 2009 5:27 PM
To: William Wagman
Cc: oracle-l_at_freelists.org
Subject: Re: Nologging clause
This is correct. The [NO]LOGGING only changes direct path operations. That is, inserts with the /*+ APPEND */ hint.
So if you want NOLOGGING you need either:
- NO ARCHIVE LOG mode
- ARCHIVE LOG mode, NOLOGGING, and APPEND hint
On Tue, Mar 31, 2009 at 5:04 PM, William Wagman <wjwagman_at_ucdavis.edu> wrote:
> It appears that he is saying that if a table is set to nologging and my insert mode is append then even if archive logging is on no redo will be generated. I'm still not sure I am understanding this correctly but I take that to mean
>
> SQL> insert /*+ APPEND */ into <table>;
>
> Then no redo will be generated. Is that a correct understanding?
-- Regards, Greg Rahn http://structureddata.org -- http://www.freelists.org/webpage/oracle-lReceived on Wed Apr 01 2009 - 10:58:15 CDT