Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Reducing Redo Log

Re: Reducing Redo Log

From: Eugen Nyffeler <eugen.nyffeler_at_ubs.com>
Date: 1998/06/09
Message-ID: <357D01AE.73E4072B@ubs.com>#1/1

Razer99 wrote:
>
> Along a similar track.
> I have a client from the mainframe world who would like
> to COMPLETELY turn off redo logs at night for
> batch processing. I disagree with this, but...
>
> Is their anyway to do that with having to alert all the tables?
> Could you redirect the redo logs to /dev/null
>
> As I recall the Oracle books state that you
> MUST have at least two redo logs at all times.
>
> rick tucker
> razer99_at_aol.com

What do you mean with batch processing ?? If you mean data load with SQL*Loader, then you can use the option unrecoverable for direct load. If you re-create index or re-create tables you can also use the unrec. option. In all other cases there's no such option as to disable the redo files (to my knowledge).

If you redirect the redo's to /dev/null (if it's possible), i think the db would work during the batch process, but Oracle changes the SNC's and if you have to do a restore sometimes later you're missing this logs (because of /dev/null) and wan't be able to do a restor to point of failure.

So don't mess with redo's if you would like to have a change to do restore to PoF. And do a backup asap if you've done things which don't write redo's (including DDL's (tuncate/drop, etc).

HtH
eugen Received on Tue Jun 09 1998 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US