Thread 1 cannot allocate new log, sequence Private strand flush not complete

Alert Log File Message : Thread 1 cannot allocate new log, sequence  Private strand flush not complete

Thread 1 cannot allocate new log, sequence  Private strand flush not complete

  Current log# 2 seq# 48 mem# 0: /u02/abcd/db/apps_st/data/log02a.dbf

  Current log# 2 seq# 48 mem# 1: /u02/abcd/db/apps_st/data/log02b.dbf

Beginning log switch checkpoint up to RBA [0x31.2.10], SCN: 130842182

Thread 1 advanced to log sequence 49 (LGWR switch)

  Current log# 1 seq# 49 mem# 0: /u02/abcd/db/apps_st/data/log01a.dbf

  Current log# 1 seq# 49 mem# 1: /u02/abcd/db/apps_st/data/log01b.dbf

Solution :

These messages are not a cause for concern unless there is a significant gap in seq# between the "cannot allocate new log" message and the "advanced to log sequence" message.

This issue is infact not a bug and is expected behavior.

In some cases, this message can be resolved by increasing db_writer_process value. 

NOTE : This Error is explained in Metalink Note ID : 372557.1