Cannot allocate new log - Private strand flush not complete Oracle Tips by Burleson Consulting October 19, 2007

 

Question:  I just upgraded to Oracle 10g release 2 and I keep getting this error in my alert log

Thread 1 cannot allocate new log, sequence 509
Private strand flush not complete
Current log# 2 seq# 508 mem# 0: /usr/local/o1_mf_2_2cx5wnw5_.log
Current log# 2 seq# 508 mem# 1: /usr/local/o1_mf_2_2cx5wrjk_.log

 

What causes the "private strand flush not complete" message?

 

Answer:  This is not a bug, it's the expected behavior in 10gr2.  The "private strand flush not complete" is a "noise" error, and can be disregarded because it relates to internal cache redo file management. 

 

Oracle MOSC note 372557.1 says that a "strand" is a new 10gr2 term for redo latches.  It notes that a strand is a new mechanism to assign redo latches to multiple processes, and it's related to the log_parallelism parameter.  The note says that the number of strands depends on the cpu_count.

 

When you switch redo logs you will see this alert log message since all private strands have to be flushed to the current redo log.