Re: cannot allocate log seq,

<ilamaran_at_my-deja.com> wrote in message news:8nhifp$ngb$1_at_nnrp1.deja.com...
> Every night at a particular time, in my production i got a message
>
>
> cannot allocate log sequence,
> Thread 1 advanced log sequence
>
> I already added log members also and increaseing the log
> buffer in the init file,after shutdown and restart. I have
> increase the checkpoint time intervel to 11000 but i got the same
> message in the alert file. Any one suggest me maran
>

The problem is that you are coming back to the first log before it has been successfully checkpointed and/or archived. The cure for that is NOT to make the logs bigger (because bigger logs switch more slowly, but they also take more time to checkpoint and archive). You need to add new redo log GROUPS (not members), so that instead of switching back to the log group being checkpointed/archived you switch onwards to a different group entirely.

If you find yourself STILL switching back on top of yourself too quickly, then a possible solution is to start fiddling with settings like log_checkpoint_interval and log_checkpoint_timeout, so that you start checkpointing *within* a log. That means the checkpoint at a log switch has less work to do, and can presumably finish it, therefore, in time. That won't help you, however, if the problem is that ARCH is too slow, since ARCH can only ever archive completed files at a proper log switch.

If you are going to set log_checkpoint_interval, how you set it depends a bit on what version of Oracle you have -but you should consider DECREASING it, not increasing it.

Regards
HJR
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Fri Aug 18 2000 - 18:00:30 CDT