Re: Consequence of switching to ARCHIVE = False without Alter Database Noarch cmd

Home -> Community -> Usenet -> c.d.o.server -> Re: Consequence of switching to ARCHIVE = False without Alter Database Noarch cmd

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Fri, 1 Nov 2002 22:44:24 +1000
Message-ID: <SBtw9.67170$g9.189446@newsfeeds.bigpond.com>

Hi Ton,

All will be well until the time comes to overwrite the redo log you started with.

It will not have been archived, as you've turned off automatic archiving but Oracle will refuse to over write it as the database is still in archivelog mode.

Hence LGWR is unable to write down to the redo log hence the redo log buffer gets full.

Hence transactions are unable to complete as they can't write to the full redo log buffer.

Hence the term "database is running that a stunned mullet" comes to mind ;)

Not a good consequence.

Cheers

Richard
"Ton" <76434.1353_at_compuserve.com> wrote in message news:4477604.0211010313.7c9afb11_at_posting.google.com...
> Can someone tell me what will happen if:
>
> -The database is in automatic archive mode
> -I Change the parameter to LOG_ARCHIVE_START=FALSE
> -Shutdown the database
> -Restart the database without executing " alter database noarchivelog " ??
>
> Thanks
Received on Fri Nov 01 2002 - 06:44:24 CST