Re: Transaction Gradually Slows to a crawl! (please help)

Richard Foote wrote:

> <snipped>
>
>
> Hi Daniel,
>
> Disabling redo logging effectively disables incremental checkpointing.
>
> Remember, why does Oracle perform checkpointing. To have a consistent point
> of time from which it can perform an instance recovery. However, by
> disabling redo logging we of course are not protecting our transactional
> changes, nothing is being written to the redo logs.
>
> So what would happen if we had an instance failure during this period of no
> redo logging. Well, we would be stuffed (Aussie technical term meaning
> Buggered). The database would be in an unrecoverable state.
>
> This is not a pretty scenario so that's why *extreme caution* must be
> exercised if anyone was silly enough to do this. In my case when I took the
> plunge, it was with the knowledge that if anything were to go wrong with the
> conversion, I could always perform a complete restore from backup.
>
> Cheers
>
> Richard

Thanks.

Sounds to me like something that might be reserved only for those rare situations such as the one you describe. Unfortunately I expect some will see this as a license to do stupid stuff and make a huge mess. Oh well!

--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)