Re: Transaction without redolog

Stefan <sroesch3_at_attbi.com> wrote in message news:<OPwZ7.4916$Sf2.45726_at_rwcrnsc52>...

> If oracle support ever detects you have set this parameter you
> lost support for the lifetime of this instance.
>
> So don't use it. Better solution is to set the table to nologging.
> But use it only for tables where a backup is performed afterwards.
> If the information isn't needed afterwards you may look into global
> temporary tables.
>
> Stefan
>

I think nologging does not mean that transactions on that table are not logged. It only means that DDLs of that table are not logged. So this would not resolve this issue.

Also, I believe _disable_logging can not be used in this case, as you can not disable logging while running archivelog mode. You would have to turn archive off - at least it was this case in 7.3.4. The original posting was asking if there is anyway to bypass redo in archive mode.

_disable_logging does have its value in import or SQLloader where you can reperform the task in case it fails. It is about 200% faster. However, if you have a shutdown abort or crash in the middle, you will lose the entire database. So you should do a cold backup before turning on this parameter. And of course Oracle would not support this. Received on Mon Jan 07 2002 - 13:20:50 CST