Re: LOGGING vs NOLOGGING

From: tmgn <tmgn_at_excite.com>
Date: Fri, 20 Aug 1999 10:05:06 -0400
Message-ID: <37BD6092.75CAF7FF@excite.com>

You are Right, Temp Segments do not generate REdo Information(Oracle is Brilliant is'nt it :)) and hence you do not need to worry about them.

It is better to Create a Huge Index with Nologging option to prevent lots of Redo Generation(affects performance drastically) and avoids LOG_ARCH_DEST fill up problems ets.
But make sure that the following Day's Backup runs fine. Otherwise you need to Create it manually in case of a Database Crash ,which could be painful..

-Thiru

dougcoan_at_my-deja.com wrote:

> Ok, This should be a no brainer, but I'm having a mental block on this:
>
> Does anyone have any thoughts on the pros/cons of setting temporary
> tablespaces to nologging? Does writing to temporary segment even
> produce redo information? I'm 99.9% sure it does not. If does, pros =
> speed and reduced log switching. Cons = I can thing of none.
>
> Also, What about setting indexes to nologging and leaving the table in
> log mode. pros = speed and reduced log switching. Cons = Must rebuild
> the indexes after recovery.
>
> Any comments welcome. Thanks..........
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
Received on Fri Aug 20 1999 - 09:05:06 CDT