The wait event log buffer space is the direct result of spending too much time allocating space in the redo buffer so redo can be copied into the just-allocated space.

As an example of how this can occur regardless of the Oracle release, referring back to Figure 8-3, suppose there was an unfortunate combination of the last allocation pointer to marker MK100 and a number of bytes large enough to push the last allocation marker clockwise beyond the last write pointer (MK300) to marker MK400. Oracle will not allow this to occur, since the redo between marker MK300 and MK400 would be overwritten. When this situation arises, the server process will post a log buffer space wait event, trigger the log writer background process to write, and wait until the log writer background process flushes the redo log buffer and moves the last write pointer beyond marker MK400. Once this takes place, the last allocation pointer will point to MK400, and the last write pointer will be set beyond marker MK400, perhaps to marker MK500.

The log buffer space wait event is most common when a system is initially placed into production or a dramatic increase in redo generation occurs. Either way, a wonderfully simplistic Oracle-focused solution that usually fixes the problem is to increase the redo log buffer size by increasing the instance parameter log_buffer. However, besides wasting memory, if the log buffer becomes too large, other wait events, such as log file sync, can arise. So be conservative to avoid introducing other problems.