- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
1#
发表于 2011-11-3 22:25:11
|
查看: 8996 |
回复: 20
T rending is very important for database performance
analysis. It exposes the performance profile of a
database in terms of IO, CPU usage, wait-event response
time, etc. Starting in Oracle Database 10g, AWR performance
data that is collected and stored out of the box is very helpful
in creating historical and comparative trend analysis to
gain insight into critical database performance issues. AWR
provides a rich history of Oracle performance statistics that
shows how an Oracle database system has been trending for
as long as the AWR data is retained.
So Where Do We Start?
Any statistic in AWR can be trended quite easily. The AWR report consists of
SQLs running against various “DBA_HIST_%” views taking the difference
between two snapshots at a time. This implies that we can develop and execute
similar SQL against those views to report the trend for any required statistic or
database wait event.
Oracle AWR (Automatic Workload Repository) Trending.pdf
(5.17 MB, 下载次数: 2006)
|
|