Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!colt.net!nntp.theplanet.net!inewsm1.nntp.theplanet.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!news.belwue.de!not-for-mail
From: Holger Baer <holger.baer@science-computing.de>
Newsgroups: comp.databases.oracle.server
Subject: Re: truncate /*+append*/
Date: Fri, 03 Mar 2006 17:32:49 +0100
Organization: InterNetNews at News.BelWue.DE (Stuttgart, Germany)
Lines: 35
Message-ID: <du9r3i$qic$1@news.BelWue.DE>
References: <1141328588.206530.61630@p10g2000cwp.googlegroups.com>   <pan.2006.03.02.20.06.01.690463@telus.net>   <1141331016.239208.326430@i40g2000cwc.googlegroups.com>   <du94ea$a6r$1@news.BelWue.DE>   <pan.2006.03.03.14.12.22.656863@sbcglobal.net> <1141402459.659701.130480@i39g2000cwa.googlegroups.com>
NNTP-Posting-Host: blackhole.science-computing.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.BelWue.DE 1141403570 27212 193.197.16.3 (3 Mar 2006 16:32:50 GMT)
X-Complaints-To: news@news.belwue.de
NNTP-Posting-Date: Fri, 3 Mar 2006 16:32:50 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060220
X-Accept-Language: en-us, en
In-Reply-To: <1141402459.659701.130480@i39g2000cwa.googlegroups.com>
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:262717

thomas.kyte@oracle.com wrote:
> Mladen Gogala wrote:
> 
>>On Fri, 03 Mar 2006 11:06:00 +0100, Holger Baer wrote:
>>
>>
>>>According to the expert, no undo will be generated *IF USING NOLOGGING* option.
>>>Try to read and understand what you cite.
>>>
>>>Regards,
>>>Holger
>>
> 
> that is not what I've said - insert /*+ APPEND */ will bypass UNDO
> generation for the table data (but not any indexes on said table).
> 
> It will bypass redo generation for the table (but never the indexes) IF
> the database is noarchivelog OR nologging has been set on the table,
> else full logging is performed for the table data (then there is that
> force logging that can affect this as well at the database level)
> 
> undo to protect the dictionary (and redo) entries that are made to
> advance the high water mark will of course be generated.
> 

Sorry for misquoting you, obviously I should follow the same advice
that I give.

I was preparing a more concise follow-up, but since its not finished
yet, and examples are missing too, this seems to be something for the
weekend to investigate (so that I'll be able to remember that correctly).

Thanks for the well deserved correction

Holger
