Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Disabling redo and rollback
Forgot one thing: if you disable logging, and then get away with doing the
import, you would really then need to shutdown the database again and
perform *another* closed, full backup.
So that's two backups and a bounce, not just one. It's worse than I thought!
Regards
HJR
"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
news:kM_V9.26687$jM5.69892_at_newsfeeds.bigpond.com...
>
> "Phil Kaufman" <philk_at_dbcsmartsoftware.com> wrote in message
> news:B4_V9.13$A9.2345076_at_mantis.golden.net...
> > Folks,
> >
> > My environment is Oracle 8.0.5 and higher/Windows 2000.
> >
> > My question may seem fairly novice, but here it is. I have written a
> > in-house export/import program, which works on multivendor databases.
At
> > any rate, I was wondering if it is possible to disable the redo and
> rollback
> > for a transaction that does the import, and if so, how exactly I would
do
> > this, and if so, what kind of improvement in performance can I expect.
> >
>
>
> You can't ever disable rollback. Unless you do discrete transactions, that
> is... which import isn't doing. Redo can't be switched off either,
> officially... except by doing a NOLOGGING transaction, which import
doesn't
> do. However, there is a hidden parameter called _disable_logging (and yes,
> that's an underscore at the beginning of it). Stick that in your init.ora,
> and set it to true. Bounce the instance. Voila.
>
> However, it's a hidden parameter for a reason: it's lethal. If you had a
> crash, power failure or a shutdown abort in the middle of your import,
your
> database would be totally kacked up, without the slightest possibility of
> recovering it or making it in any way usable thereafter.
>
> A prior complete, cold backup would solve that problem, of course... but
> then it will probably take you as long to do the backup+bounce as it would
> have done to perform the import in the first place.
>
> Anyways: those are your choices.
>
> Personally, I'd forget all about it, and just let import do its thing.
>
> Regards
> HJR
>
>
>
> > Thanks!
> >
> >
>
>
Received on Fri Jan 17 2003 - 15:53:43 CST