RE: sequential read on full-table scan?

I see a long discussion here about db file sequential read in a FTS.
I have discovered an interesting opposite case - a multi block read
(db file scattered read) for INDEX UNIQUE SCAN operation that is
typically a single block read operation.

I turned on event 10299 as well to trace prefetched blocks and below one
can see the excerpt from event 10046+10299 trace file. Obviously in =
version
10.1.0.3 Oracle is capable to do such optimization. Instead of reading 1 =
block
at a time Oracle reads 13 blocks in one multiblock read and 12 of them =
are
prefetched. Of course there are also some single block reads.

Below are the details. The statement is a simple update statement that
updates by primary key.

sorry folks -- I was just reading my own post, and I see the text is =
confusing.
"This obviously also includes blocks containing overflow row pieces"
refers to all blocks below the HWM being read into the buffer cache by a =
full
table scan.
kind regards,