Re: "_disable_logging" parameter

> but with "_disable_logging" enabled will this necessitate recovery from
> a cold backup ???

Actually, disable logging means, do not generate redo, if you have a powerfailure, or a shutdown abort for any which reason, at startup oracle needs the redo to recover the datafiles. Thus yes you will be in trouble and have to go back to the last cold backup. Basically what _disable_logging could (if at all ...) be used for is to do a one time load of a huge system or so, and after the load, do a cold backup, and startup again with _disable_logging turned off. So that if afterwards something goes wrong, you have your backup. Running a database in _disable_logging mode is asking for trouble. even if it is development... if the littlest thing happens. you're screwed. Someone kills a background process, there is a system crash or an oracle abnormal shutdown and you ve had it. Do you want to take this risk ?

When it comes to redologfiles, I suggest the one major thing you can do is (if there is such an update/change load on your database) put them on seperate devices. Have you done a bstat/estat yet ? Do you know where the major performance issues are ? Maybe try to do a generic tuning, oracle allows a lot of tuning to be done.

Cheers
Wim Received on Wed Jan 14 1998 - 00:00:00 CST