cell smart index scan等待事件

简介:
This is an Exadata wait event that occurs when fast full index scans are offloaded to the storage cells. This event is related to cell smart table scan except that the object is an index. This event does not show up very frequently in Exadata probably because it is very good at performing full table scans and index reads may actually be less efficient. Also, only full fast scans (not range or full scans) of indexes are eligible for smart scans, which reduces the likelihood of seeing this event.    

 

Solutions

Offloading the index scans to the storage cells within an Exadata machine is probably a good thing, so there may be no tuning required. However, if you have a query that waits extensively on this wait event, it may mean that query tuning is required so it utilizes indexes more effectively. Also review the Objects tab in Ignite to understand which is causing the most wait time.



本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1277895

相关文章
|
SQL 存储 Oracle
PostgreSQL 分页, offset, 返回顺序, 扫描方法原理(seqscan, index scan, index only scan, bitmap scan, parallel xx scan),游标
PostgreSQL 分页, offset, 返回顺序, 扫描方法原理(seqscan, index scan, index only scan, bitmap scan, parallel xx scan),游标
3834 0
|
SQL 索引
ORA-01502: index ‘index_name' or partition of such index is in unusable state
错误现象:   今天发布脚本时,一个表插入数据时报如下错误   ORA-01502: index ‘index_name' or partition of such index is in unusable state   ORA-06512: at line 168 错误原因:   这个错误一般是因为索引状态为UNUSABLE引起的。
982 0
|
数据库管理 关系型数据库 Oracle