direct path read temp等待事件
2013-03-19 00:47
477 查看
Often related to sorting operations, check to see if occurring primarily in temp tablespaces.
Solutions
1) Reading from temp tablespaces
If the database parameter workarea_size_policy = AUTO:
Increase the database parameter pga_aggregate_target.
Otherwise:
Increase the database parameter sort_area_size.
Another possible solution is to cache the temp datafile at the O/S or Storage system level.
2) Reading application data
Ensure database parameter, DISK_ASYNC_IO is TRUE
Ensure no disks are I/O bound.
Ensure the OS asynchronous I/O is configured correctly.
During Direct Path operations the data is asynchronously read from the database files. At some point the session needs to make sure that all outstanding asynchronous I/O have been completed to disk. This can also happen if, during a direct read, no more slots are available to store outstanding load requests (a load request could consist of multiple I/Os). Direct path reads are generally used by Oracle when reading directly into PGA memory (as opposed to into the buffer cache). If asynchronous I/O is supported (and in use) then Oracle can submit I/O requests and continue processing. It can then pick up the results of the I/O request later and will wait on "direct path read" until the required I/O completes.
Solutions
1) Reading from temp tablespaces
If the database parameter workarea_size_policy = AUTO:
Increase the database parameter pga_aggregate_target.
Otherwise:
Increase the database parameter sort_area_size.
Another possible solution is to cache the temp datafile at the O/S or Storage system level.
2) Reading application data
Ensure database parameter, DISK_ASYNC_IO is TRUE
Ensure no disks are I/O bound.
Ensure the OS asynchronous I/O is configured correctly.
During Direct Path operations the data is asynchronously read from the database files. At some point the session needs to make sure that all outstanding asynchronous I/O have been completed to disk. This can also happen if, during a direct read, no more slots are available to store outstanding load requests (a load request could consist of multiple I/Os). Direct path reads are generally used by Oracle when reading directly into PGA memory (as opposed to into the buffer cache). If asynchronous I/O is supported (and in use) then Oracle can submit I/O requests and continue processing. It can then pick up the results of the I/O request later and will wait on "direct path read" until the required I/O completes.
相关文章推荐
- I/O上的等待事件 —— direct path read temp、direct path write temp
- direct path read temp等待事件
- Oracle 11g direct path read 等待事件的理解
- oracle等待事件-direct path read/write
- oracle等待事件2构造一个DB File Sequential Read等待事件和构造一个Direct Path Read
- direct path read等待事件
- direct path write temp等待事件
- Oracle 11g direct path read 等待事件的理解
- direct path write temp等待事件
- I/O上的等待事件 —— direct path read、direct path write
- direct path read 等待事件分析
- oracle非空闲的等待事件-direct path read
- 非空闲的等待事件-direct path read
- Oracle direct path read 事件解释
- direct path read temp
- direct path write等待事件
- direct path write等待事件
- direct path read temp
- 查询v$lock缓慢和direct path write temp等待
- 查询v$lock缓慢和direct path write temp等待