Figure 7-5 is nearly identical to Figure 7-3, with the key exception that the contents are filled based on the SQL run in Figure 7-4, which produced the trace file shown in Figures 7-6 and 7-7. (The trace file was simply too large to place in a single figure.)

Figure 7-5 shows bucket 14778 is associated with the cursor that has two identical SQL statements, yet an optimizer parameter was altered between their execution, creating the two child cursors. Notice both the parent and child cursors have the same type: CRSR. If you look closely at the top of the Figure 7-6 trace file, you'll see bucket 14778, its associated handle, mutex, name, and two child cursors, each with a handle. Bucket 60635 is associated with one object: the findme table with its handle 456df410.

Figure 7-6. The first part of the trace file created by the SQL in Figure 7-4. This part contains the hash bucket chain details. This text is diagrammed in Figure 7-5. While no lines have been modified, many lines have been removed.