Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 








Cannot allocate new log - Private strand flush not complete

Oracle Database Tips by Donald Burleson

October 19, 2015


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


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


Answer:  This is not a bug, it's the expected behavior in 10gr2.  You can get the message suppressed by increasing the db_writer_processes parameter.

The "private strand flush not complete" is a "noise" error, and can be disregarded because it relates to internal cache redo file management.  It does not necessarily mean that you have a problem, but it depends if the error message is accompanied by other errors.


You should check your transaction with used private redo size in the x$ktifp fixed table  or why the DBWR wants to write these associated blocks so fast if you have a lot of "Private  strand flush not complete" messages.


This "private strand flush cannot complete" error is sometimes accompanied by other errors/mistakes that cause a hung database.  

  • Some DBA's blame a sub-optimal DBWR configuration for the "private strand flush not complete" error.  See "DB_WRITER_PROCESSES" MOSC 67422.1, and "Understanding and Tuning Buffer Cache and DBWR", MOSC Note: 62172.1.

  • Some DBA's note that this error message can be caused by a too-full datafile.  Check your data file space, and add space to any nearly full data files.

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 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.


References:  Oracle MOSC note 372557.1

Oracle Training from Don Burleson 

The best on site "Oracle training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!

Oracle training



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.