A server process is waiting on “db file sequential read” wait event after it performs a single block I/O operation and it is waiting for the operating system to complete it.

A single block I/O operation occurs when a server process request a single block for the operating system. This happens during operations such as index unique or range scans, table access by rowid, etc.

Seeing this wait event in the top wait events is expected and doesn’t mean that something is wrong. Remember, users are working and reading indexes or table blocks from the disk is common. However, if we see that this event is very high and consuming unreasonable time, we need to check our SQL statement, they might need tuning, or might have unnecessary hints such as the “index” hint.