"Richard Foote" <richard.foote_at_bigpond.com> wrote:
>
>"Ruthf" <ruthf_at_tvuna.co.il> wrote in message
>news:48580dac.0309170324.49e65049_at_posting.google.com...
>> We changed our server from ARCHIVE to NO ARCHIVE mode.
>> WHY DO I GET THE FOLLOWING ERROR ???????????
>>
>> Thread 1 cannot allocate new log, sequence 2107
>> All online logs needed archiving
>> Current log# 1 seq# 2106 mem# 0: E:\ORACLE\ORADATA\ORC1\REDO01_N.LOG
>> Current log# 1 seq# 2106 mem# 1: H:\ORACLE\ORADATA\REDO01_2.LOG
>
>Hi Ruthf,
>
>Having placed your database in archivelog mode, Oracle will not overwrite a
>redo log group unless it has been appropriately archived. In the above case,
>none of your redo logs have been archived to Oracle's satisfaction.
>
>My guess is that you haven't started the ARCH process (via the
>log_archive_start parameter) hence you're database sitting like a stunned
>mullet. That said, if you're unable to archive any of your mandatory
>destinations or you're unable to satisfy the log_archive_min_succeed_dest
>parameter, you could be likewise stuffed.
>
>Still reckon you haven't started the archive process though ...
>
>Good Luck
>
>Richard
>
The OP indicated that they have changed to NOARCHIVELOG mode..I suspect that they did not STOP the ARCH process..Or
'bounce' the instance.
Received on Wed Sep 17 2003 - 08:53:26 CDT
