Db file sequential read

WAIT #256: nam='db file sequential read' ela= 1 p1=19 p2=90569 p3=1 WAIT #256: nam='db file sequential read' ela= 0 p1=43 p2=1303949 p3=1 WAIT #256: nam='db file sequential read' ela= 1 p1=19 p2= db file sequential read. Среднее время этого ожидания = фактическому среднему времени чтения одного блока БД (что на уровне ОС обычно называют выборочным или случайным чтением (random read)). 29 OLUSER14 db file sequential read 12 WAITED KNOWN TIME 1. 32 ID2USER db file scattered read О WAITING О. Сеанс 29 ожидает события. db file sequential read. db file single write. DFS db file lock. free global transaction table entry. free process state object. global cache lock cleanup. db file sequential read (F, B). db file scattered read (F, B). direct path read (F, B). direct path write (F, B). db file parallel write (B). 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. Например, в случае "db file sequential read" p1 содержит номер читаемого файла, а p2 - номер читаемого блока. Поэтому можно использовать значения столбцов p1 и p2, чтобы по представлению DBA_EXTENTS If CPU time spent is 'x' secs then Elapsed time was '2x', and the waits listed below in the trace just contribute to a single wait event 'db file sequential read' Now we are loading data in какого хрена db file sequential read может идти по несколько минут один блок (8K)? Личный Кабинет Удалён (155), закрыт 7 лет назад. Any tricks on how to found out why there are such an enormous reads for "db file sequential read"? The db_file_multiblock_read_count is not set, so Oracle has the responsibility for that parameter.