Some DBAs have experienced this seemingly strange phenomenon. Their story is very similar: During nightly batch processing, many blocks were changed. When the employees arrived in the morning and started querying the database, the DBA noticed a lot of redo being generated. So, what may seem like an anomaly makes perfect sense after all.

Compared to the buffer cache and shared pool memory structures, the redo log buffer is very straightforward. While Oracle continues to enhance the redo log buffer architecture, the central idea has remained the same: buffer and batch redo changes to improve log writer background process efficiency and enable extremely quick commit times.

Figure 8-3 is a highly abstracted view of the redo log buffer and is more accurate for Oracle releases prior to Oracle9i Release 2, but it is a great way to gain a solid conceptual view of the redo log buffer and how it works. The redo log buffer is a circular first-in/first-out (FIFO) queue structure. The structure also utilizes two pointers: