Now that we have identified the buffer busy pattern, the object type, and whether the block is a header block, we have enough information to proceed directly to a list of possible solutions.

The reason why buffer busy waits events give firefighters so much trouble is that before they can get to an appropriate (and I stress appropriate) solution set, they must first determine the busy pattern, the block's segment type, and if the block is a header block. With this information, we are now ready to jump to a very specific solution set. Solutions for the most common buffer busy situations are presented in the following sections.

If the same single buffer is nearly always the busy buffer, then we need to figure out why. In our example, a group of buffers were busy, including buffer 4,54; that is, not just a single buffer was nearly always busy. But if there is a single busy buffer, you need to clearly understand what information is being stored in the block (perhaps query the rows just in that block) and why the application is so interested in the block.