Re: Oracle on ram drive with no redo log or other archiving

robertbrown1971_at_yahoo.com wrote:
>
> I know this will be very grating for the experts to hear but in this

You got that right!
<grating sound>

> Question:
>
> 1) How can I start oracle to minimize or disable redo log? I know there
> is a NOARCHIVE mode. Is that it? How do I enable it for the whole
> instance?

Like someone else said, google for that parameter. And hope it works in your particular version.

> 2) What other logs are there and how can I turn them off (or minimize
> output)

Redo logs are it.

> 3) What other files besides that data files for the tablespaces used by
> tests need to be in RAM drive for fastest performance. In other words,
> if I have a regular oracle account and just execute vanilla updates
> where does Oracle write to besides the redo log and the data files.

Undo tablespace is one. If you update/delete (as opposed to insert) you're virtually guaranteed to use up large amounts of this. The other lesser known one is the controlfile: it gets written a lot in normal operation. Keep it in RAM as well. And you'll have no hope in heck of ever getting that db back if there is a glitch in memory, I think you realize that?

> Note that not all are in RAM. Since ram is expensive it would be
> preferrable to keep the files that are changing rarely in durable
> location and then only put the files that actually affect performance
> on the ram drive.

Sensible. Although I still can't see what you folks trying to prove. Keep us posted on results. Received on Tue Oct 04 2005 - 19:25:58 CDT