标签:Tables RAC HR instances Hot owner name
Hot Tables in RAC Tuning
When tuning storage, it is often beneficial to be able to identify hot spots in the databases, i.e. tables with more I/O activity than others. The v$segment_statistics view can be used to generate a list of objects order by read and write operations similar to the following:
< hot_segments.sql
select
owner,
object_name,
sum(value) as total_ios
from
gv$segment_statistics
where
(statistic_name like 'physical%read%'
or statistic_name like 'physical%write%')
and
owner not in ('SYS','XDB','SYSTEM','APEX_030200','MDSYS',
'WMSYS','DBSNMP','EXFSYS','AUDSYS','GSMADMIN_INTERNAL')
group by
owner,
object_name
order by
sum(value) desc;
OWNER OBJECT_NAME TOTAL_IOS
---------- --------------- ----------
SCOTT DEPTS 6574
SCOTT DEPTS_PK 354
HR EMPLOYEES 184
HR EMP_EMP_ID_PK 18
HR DEPARTMENTS 8
Even in single-instance databases, the above query is beneficial to be able to identify hot spots. Tables and indexes at the top of the list are candidates to be on separate disks so as to reduce disk contention. For Oracle RAC databases, one may also want to consider using application partitioning to access the segments from different instances, if possible. In the example above, there are two schemas shown and those applications may use different services. While separating the segments to different instances will not cut down on the I/O operations, it will reduce global cache transfers between instances.
标签:Tables,RAC,HR,instances,Hot,owner,name 来源: https://www.cnblogs.com/yaoyangding/p/15164747.html
本站声明: 1. iCode9 技术分享网(下文简称本站)提供的所有内容,仅供技术学习、探讨和分享; 2. 关于本站的所有留言、评论、转载及引用,纯属内容发起人的个人观点,与本站观点和立场无关; 3. 关于本站的所有言论和文字,纯属内容发起人的个人观点,与本站观点和立场无关; 4. 本站文章均是网友提供,不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属;如您发现该文章侵犯了您的权益,可联系我们第一时间进行删除; 5. 本站为非盈利性的个人网站,所有内容不会用来进行牟利,也不会利用任何形式的广告来间接获益,纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。