Hi Experts.

I'm getting this "cannot allocate new log" message in my alert.log file.

It seems to be able to proceed to the next log sequence number anyway,
so should I be worried about this?

Thread 1 advanced to log sequence 6595
Current log# 1 seq# 6595 mem# 0: /u03/oradata/chpdr/redo01_a.log
Current log# 1 seq# 6595 mem# 1: /u03/oradata/chpdr/redo01_b.log
Tue Apr 29 05:08:41 2008
Thread 1 advanced to log sequence 6596
Current log# 2 seq# 6596 mem# 0: /u03/oradata/chpdr/redo02_a.log
Current log# 2 seq# 6596 mem# 1: /u03/oradata/chpdr/redo02_b.log
Tue Apr 29 05:11:48 2008
Thread 1 cannot allocate new log, sequence 6597
Private strand flush not complete
Current log# 2 seq# 6596 mem# 0: /u03/oradata/chpdr/redo02_a.log
Current log# 2 seq# 6596 mem# 1: /u03/oradata/chpdr/redo02_b.log
Thread 1 advanced to log sequence 6597
Current log# 3 seq# 6597 mem# 0: /u03/oradata/chpdr/redo03_a.log
Current log# 3 seq# 6597 mem# 1: /u03/oradata/chpdr/redo03_b.log


Related question: In the same bdump directory, the archiver is writing
messages like this:

kcrrwkx: nothing to do (start)
*** 2008-04-28 07:05:17.561
kcrrwkx: nothing to do (start)
*** 2008-04-28 07:10:17.571
kcrrwkx: nothing to do (start)
*** 2008-04-28 07:15:17.581

and occasionally reports that it is shutting down one of the archive
processes.

This is not a problem, but how would I set the database to start up fewer
ARCH processes anyway?


Christopher Curzon, DBA and Data Modeler
Health Management Systems
(626) 570-6941 x3603


Oracle LazyDBA home page