{"id":114,"date":"2017-08-14T00:31:06","date_gmt":"2017-08-14T00:31:06","guid":{"rendered":"http:\/\/www.mrmarkyoung.com\/oracle\/?p=114"},"modified":"2017-08-14T00:31:06","modified_gmt":"2017-08-14T00:31:06","slug":"db-file-sequential-read-wait-event","status":"publish","type":"post","link":"http:\/\/www.mrmarkyoung.com\/oracle\/2017\/08\/14\/db-file-sequential-read-wait-event\/","title":{"rendered":"DB File Sequential Read Wait Event"},"content":{"rendered":"<p>The db file sequential read wait event has three parameters: file#, first block#, and block count. In Oracle Database 10 g , this wait event falls under the User I\/O wait class. Keep the following key thoughts in mind when dealing with the db file sequential read wait event.<\/p>\n<p>The Oracle process wants a block that is currently not in the SGA, and it is waiting for the database block to be read into the SGA from disk.<br \/>\nThe two important numbers to look for are the TIME_WAITED and AVERAGE_WAIT by individual sessions.<br \/>\nSignificant db file sequential read wait time is most likely an application issue.<\/p>\n<p>You can determine which session has high TIME_WAITED on the DB file sequential read wait event from the V$SESSION_EVENT view. The TIME_WAITED must be evaluated with the LOGON_TIME and compared with other non-idle events that belong to the session for a more accurate analysis. Sessions that have logged on for some time (days or weeks) may accumulate a good amount of time on the DB file sequential read event. In this case, a high TIME_WAITED may not be an issue. Also, when the TIME_WAITED is put in perspective with other non-idle events, it prevents you from being blindsided . You may find another wait event which is of a greater significance.\t<\/p>\n<pre class=\"lang:default decode:true \" >SELECT  a.sid, a.event, a.time_waited,\r\n        a.time_waited \/ c.sum_time_waited * 100 pct_wait_time,\r\n        ROUND((sysdate - b.logon_time) * 24) hours_connected\r\nFROM    v$session_event a, v$session b,\r\n        (SELECT sid, SUM(time_waited) sum_time_waited\r\n        FROM   v$session_event\r\n        WHERE  event NOT IN (\r\n                   'Null event',\r\n                   'client message',\r\n                   'KXFX: Execution Message Dequeue - Slave',\r\n                   'PX Deq: Execution Msg',\r\n                   'KXFQ: kxfqdeq - normal deqeue',\r\n                   'PX Deq: Table Q Normal',\r\n                   'Wait for credit - send blocked',\r\n                   'PX Deq Credit: send blkd',\r\n                   'Wait for credit - need buffer to send',\r\n                   'PX Deq Credit: need buffer',\r\n                   'Wait for credit - free buffer',\r\n                   'PX Deq Credit: free buffer',\r\n                   'parallel query dequeue wait',\r\n                   'PX Deque wait',\r\n                   'Parallel Query Idle Wait - Slaves',\r\n                   'PX Idle Wait',\r\n                   'slave wait',\r\n                   'dispatcher timer',\r\n                   'virtual circuit status',\r\n                   'pipe get',\r\n                   'rdbms ipc message',\r\n                   'rdbms ipc reply',\r\n                   'pmon timer',\r\n                   'smon timer',\r\n                   'PL\/SQL lock timer',\r\n                   'SQL*Net message from client',\r\n                   'WMON goes to sleep')\r\n       HAVING SUM(time_waited) &gt; 0 GROUP BY sid) c\r\nWHERE    a.sid = b.sid\r\nAND      a.sid = c.sid\r\nAND      a.time_waited &gt; 0\r\nAND      a.event = 'db file sequential read'\r\nORDER BY hours_connected desc, pct_wait_time;\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>The db file sequential read wait event has three parameters: file#, first block#, and block count. In Oracle Database 10 g , this wait event falls under the User I\/O wait class. Keep the following key thoughts in mind when dealing with the db file sequential read wait event. The Oracle process wants a block &#8230; <a title=\"DB File Sequential Read Wait Event\" class=\"read-more\" href=\"http:\/\/www.mrmarkyoung.com\/oracle\/2017\/08\/14\/db-file-sequential-read-wait-event\/\" aria-label=\"Read more about DB File Sequential Read Wait Event\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[25,24],"class_list":["post-114","post","type-post","status-publish","format-standard","hentry","category-oracle-database","tag-sequential","tag-wait-event"],"_links":{"self":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/comments?post=114"}],"version-history":[{"count":2,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/114\/revisions"}],"predecessor-version":[{"id":116,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/posts\/114\/revisions\/116"}],"wp:attachment":[{"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/media?parent=114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/categories?post=114"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.mrmarkyoung.com\/oracle\/wp-json\/wp\/v2\/tags?post=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}