DB file Sequential read:
Website Explanation:
This event signifies, the user process is reading a buffer to the SGA buffer cache and is waiting for a physical I/Ocall to return. A sequential read is a single-block read.
The single block I/Os is usually the result of the using indexes. Rarely, full table scan calls could get truncated to a single block call because of extent boundaries, or buffers present In the buffer cache. These waits would also show up as db file sequential read
.
Check the following V$SESSION_WAIT
parameter columns:
On a healthy system, physical read waits should is the biggest waits after the idle waits. However, also consider whether there is on db
file
sequential
reads
a large data warehouse so should be seeing mostly fu ll table scans with parallel query.
Figure 10-1 depicts the differences between the following wait events:
db
file
sequential
read
(single block, read into one SGA buffer)
db
file
scattered
read
(Multiblock read into many discontinuous SGA buffers)
direct
read
(single or multiblock read into the PGA, bypassing the SGA)
Figure 10-1 Scattered read, sequential read, and Direct Path read
650) this.width=650; "src=" Https://s1.51cto.com/wyfs02/M00/8F/84/wKiom1jjNvvyrXSCAAAuIt3LsAc079.png "title=" db File sequential read.png "alt=" Wkiom1jjnvvyrxscaaauit3lsac079.png "/>
Explain:
DB Sequential Read this event indicates that the user process is reading the buffer into the SGA buffer cache and is waiting for the physical I/O call to return. Sequential reads are single-block reads .
a single block I/O is usually the result of using an index.
full-table scan calls may be truncated by a single block called by the buffer cache for the presence of a range boundary or buffer. These waits will also be displayed as DB file sequential read.
The optimization method for DB file sequential read:
From the beginning of reading, increase the size of buffer cache in the SGA to avoid reading from the hard disk each time;
Optimization of SQL statements to reduce unnecessary block reads;
This article is from the "Linux Oracle MariaDB" blog, so be sure to keep this source http://wangergui.blog.51cto.com/8504247/1912801
DB file sequential read for Oracle wait event