Re: The Admin's point of view on DB users best practices

"Rick Denoire" <100.17706_at_germanynet.de> wrote in message news:eivs209v1hkdfksgd4iqpcmtu3fucv8nc3_at_4ax.com...
> "Ana C. Dent" <anacedent_at_hotmail.com> wrote:
>
> >Rick Denoire wrote:
> >[...snip...]
> >> 6) Always do an "insert /*+ APPEND */ " into an empty table, perhaps
> >> in nologging mode.
> >
> >TRADE-OFFS
> >
> >Do you realize that after NOLOGGING is used, you've just rendered the
> >previous hotback useless past this point in time? Since the data
> >being inserted is NOT written to the redo logfiles, any recovery of
> >this instance can only be made valid to the time of when NOLOGGING
> >is used.
>
> May be I understand something wrong, correct me please. When NOLOGGING
> has been used, recovery is still possible, but NOLOGGING
> objects/operations won't be restored; the rest, written to the redo
> files, should be recoverable.
>

You've got this part right.

> In our case, NOLOGGING is encouraged for objects containing redundant
> or reproducible data.
>
> I am still not sure about the impact of setting all indexes to
> NOLOGGING. After all, they can be dropped and recreated.
>
> Bye
> Rick Denoire
>

In the case of infrequently changed large tables, you may not want to do this because it will take much longer to recreate indexes than applying small amount of logs. Received on Sat Feb 14 2004 - 15:16:33 CST