High Waits on 'Db File Sequential Read' Due to Table Lookup Following Index Access (文档 ID 875472.1)

原创 2013年12月02日 09:16:25

In this Document

  Symptoms
  Cause
  Solution
  References

APPLIES TO:

Oracle Server - Enterprise Edition - Version 8.0.3.0 to 11.2.0.2 [Release 8.0.3 to 11.2]
Information in this document applies to any platform.

SYMPTOMS

A query can wait on 'db file sequential read' for a long time even if the execution plan appears to be optimal. 
This usually happens when the result set of index scan is large.

For example:

SELECT D
FROM BIG_TABLE
WHERE A = 1253
AND B in ('CA', 'CO')
AND C > 210 ;


Rows    Row Source Operation
------- ---------------------------------------------------
 215431 TABLE ACCESS BY INDEX ROWID BIG_TABLE (cr=880191 pr=430780 pw=0 time=2293667056 us) <<<
3582275  INDEX RANGE SCAN BIG_TABLE_IDX (cr=664748 pr=218595 pw=0 time=352506821 us)

Elapsed times include waiting on following events:
  Event waited on                             Times   Max. Wait  Total Waited
  ----------------------------------------   Waited  ----------  ------------
  SQL*Net message to client                   14363        0.00          0.02
  db file sequential read                    461688        1.15       2254.55 <<<
  SQL*Net message from client                 14363        0.01          9.77
  SQL*Net break/reset to client                   1        0.00          0.00
...

 

CAUSE

In most cases like this, the execution of the query waits on "TABLE ACCESS BY INDEX ROWID" much longer than on INDEX SCAN. It is because the random access to the table rows is much more expensive than index scan.

 

SOLUTION

You can try one or more of the following.

 

1. Check if there is a better index or plan. You may need to re-design index configuration.

 

2. Try table full scan. Full scan often runs faster than Index scan, though its CBO cost is higher than the cost of Index scan.

SELECT /*+ FULL(BIG_TABLE) */  D 
FROM BIG_TABLE 
WHERE A = 1253 
AND B in ('CA', 'CO') 
AND C > 210 ;

 

3. Create a concatenated index to avoid the table access if the query has only a few columns of the table in SELECT and WHERE clauses. 

For example:

CREATE INDEX <INDEX_NAME> ON BIG_TABLE (A, B, C, D);

 NOTE : This can only be applied to SELECT for the table. If the query updates the table, this will not help.

 

4. Move the table into the tablespace with a larger block size.  A larger block has more rows in it, so it may help to reduce block I/O.

    And it will also be helpful to reorganize the table so that the index may have a smaller clustering factor.

 

5. Consider increasing buffer cache so that more table blocks can be cached. It is a good idea to use keep buffer pool if the table is frequently accessed.

Note 76374.1 Multiple Buffer Pools

 

6. Consider using IOT(Index Organized Table). IOT may reduce I/O because it stores data in a B*Tree index structure.
   For example, if the column 'A' is the primiary key of BIG_TABLE, you can try to create IOT as follows.
   
   create table BIG_TABLE (A number primary key, B char(2), C number, D varchar2(10)) 
   organization index;

 

7. Consider using parallel execution if there is sufficient free resource(CPU, memory) in the server.
   This option does not reduce I/O. But, this may help to reduce execution time.

 

8. Bad disk I/O can be a reason. In this case, improve the I/O of devices where the table resides. This requires help from a system administrator.

REFERENCES

NOTE:34559.1 - WAITEVENT: "db file sequential read" Reference Note
NOTE:76374.1 - Multiple Buffer Pools
 
 

相关内容

   
 
版权声明:本文为博主原创文章,未经博主允许不得转载。

相关文章推荐

High Waits on 'Db File Sequential Read' Due to Table Lookup Following Index Access

最近某些系统AWR的top 5中“Db File Sequential Read”占据的时间百分比非常大,通常这种等待事件是一种正常的。但当前系统性能是有些问题的,并发量大,有些缓慢,因此需要判断这种...
  • bisal
  • bisal
  • 2013-10-19 22:59
  • 1404

ORA-39181:Only Partial Table Data Exported Due To Fine Grain Access Control [ID 422480.1]

修改时间 15-MAR-2011     类型 PROBLEM     状态 PUBLISHED   In this Document   Sympto...

Troubleshooting 'enq: TX - index contention' Waits in a RAC Environment. (文档 ID 873243.1)

In this Document   Goal   Solution   Community Discussions   References ...

Access restriction: The type is not accessible due to restriction on required library问题处理

在做Java时,遇到了个小问题,在Import 包资源时出现:        Access restriction: The type XXX is not accessible due to re...

How to Switch the Driving Table in a Hash Join (文档 ID 171940.1)

************************************************************* This article is being delivered in Dr...

dbca建库遭遇Could not connect to ASM due to following error:ORA-01017

环境描述:AIX6.1+Oracle11gRAC(11.2.4)+双节点 dbca建库过程中遇到Could not connect to ASM due to following error:ORA...

How to Check Device UUID or File System UUID. (文档 ID 1505398.1)

How to Check Device UUID or File System UUID. (文档 ID 1505398.1) 如何检测设备的UUID或者文件系统的UUID 转到底部 ...

ONT-How to Create a Debug File in Shipping Execution (文档 ID 290432.1)

转自:https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=425753385590544&parent=DOCUMENT&s...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:深度学习:神经网络中的前向传播和反向传播算法推导
举报原因:
原因补充:

(最多只允许输入30个字)