Re: table nologging in 8i

steve, thanks for the reply. It is true that deleting is no logged when table is in nologging mode ? what view are you using to monitor redo and undo consumption v$sysstat or v$transaction. thanks again ted

In article <FR+W5vAUwfh5EwkY_at_rwx777.demon.co.uk>,   Steve Haynes <steve_at_rwx777.demon.co.uk> wrote:
> In article <8m4o0s$fl5$1_at_news.bentley.com>, Tom Best
> <tom.best_at_bentley.com> writes
> >Ted:
> >
> >No.
> >
> >HTH,
> >Tom Best
> >
> Yes, nologging just means nologging of current action.
> ie: it will be an unrecoverable action.
> This is a limited, dubious feature in my book. The risks
> outweigh the advantages. Nologging on create index is
> about 3X quicker though in my experience. In this case
> (where indexes can easily be rebuilt), it's worth it.
>
> I've heard many opinions on this and (I think) finally
> got to the bottom of it... eventually... with oracle support.
>
> You can't turn off logging on a table at a transaction level
> (for any transaction) or it could never rollforward.
> Commit only means commit to redo log, not commit to datafile.
>
> Feel free to correct me, but I did dig pretty hard on this
> since I originally wanted to turn off logging everywhere
> for speed, we did full cold backups so I couldn't see the
> need for logging (at the time).
>
> Steve
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Aug 01 2000 - 00:00:00 CDT