这几天数据库上的用户表空间疯涨,一天的增长量达到了20~30GB,平时就4~5GB的增长量。问了开发商,他们也说不出个所以然。PS:那些鸟开发商,现在我已经对他们绝望了,什么都不知道。情急之下直接对该表空间进行了扩容,问题总算解决了。事后总想弄个明白,想知道是那张表导致的表空间增长如此之快,以免下次出现同样的问题又是不知所措。
google了一番后发现DBA_HIST_SEG_STAT可以看出对象的使用趋势
构造如下SQL查询出每个时间段内数据库对象的增长量,其中DB_BLOCK_CHANGES_DELTA为块个数
select c.SNAP_ID,to_char(c.END_INTERVAL_TIME,'yyyy-mm-dd') SNAP_TIME,a.OWNER ,a.OBJECT_NAME, a.OBJECT_TYPE, b.DB_BLOCK_CHANGES_DELTA
from dba_objects a,
(select SNAP_ID,obj#,DB_BLOCK_CHANGES_DELTA from DBA_HIST_SEG_STAT where DB_BLOCK_CHANGES_DELTA > 20000 order by snap_id desc, DB_BLOCK_CHANGES_DELTA desc) b,
DBA_HIST_SNAPSHOT c
where a.object_id=b.obj# and object_type='TABLE' and b.SNAP_ID=c.SNAP_ID
order by DB_BLOCK_CHANGES_DELTA
下面的SQL查询出某个时间段内,数据库对象的变化大小,单位以换算成GB
select a.OBJECT_NAME, to_char(c.END_INTERVAL_TIME,'yyyy-mm-dd') SNAP_TIME, sum(b.DB_BLOCK_CHANGES_DELTA)/1024/1024 GB from dba_objects a,(select SNAP_ID,obj#,DB_BLOCK_CHANGES_DELTA from DBA_HIST_SEG_STAT where DB_BLOCK_CHANGES_DELTA > 20000 order by snap_id desc, DB_BLOCK_CHANGES_DELTA desc) b,DBA_HIST_SNAPSHOT c
where a.object_id=b.obj# and object_type='TABLE' and b.SNAP_ID=c.SNAP_ID
group by a.OBJECT_NAME,c.END_INTERVAL_TIME
order by GB
简单介绍下DBA_HIST_SEG_STAT
DBA_HIST_SEG_STAT视图内记录了数据库实例启动以来段的变化信息,该视图的数据来自于v$segstat
Column | Datatype | NULL | Description |
| |
| Unique snapshot ID |
| |
| Database ID for the snapshot |
| |
| Instance number for the snapshot |
| |
| Tablespace number |
| |
| Dictionary object number |
| |
| Data object number |
| |
| Cumulative value for logical reads |
| |
| Delta value for logical reads |
| |
| Cumulative value for buffer busy waits |
| |
| Delta value for buffer busy waits |
| |
| Cumulative value for db block changes |
| |
| Delta value for db block changes |
| |
| Cumulative value for physical reads |
| |
| Delta value for physical reads |
| |
| Cumulative value for physical writes |
| |
| Delta value for physical writes |
| |
| Cumulative value for physical reads direct |
| |
| Delta value for physical reads direct |
| |
| Cumulative value for physical writes direct |
| |
| Delta value for physical writes direct |
| |
| Cumulative value for ITL waits |
| |
| Delta value for ITL waits |
| |
| Cumulative value for row lock waits |
| |
| Delta value for row lock waits |
| |
| Cumulative value for global cache CR blocks served |
| |
| Delta value for global cache CR blocks served |
| |
| Cumulative value for global cache current blocks served |
| |
| Delta value for global cache current blocks served |
| |
| Cumulative value for global cache buffer busy |
| |
| Delta value for global cache buffer busy |
| |
| Cumulative value for global cache CR blocks received |
| |
| Delta value for global cache CR blocks received |
| |
| Cumulative value for global cache current blocks received |
| |
| Delta value for global cache current blocks received |
| |
| Cumulative value for space used |
| |
| Delta value for space used |
| |
| Cumulative value for space allocated |
| |
| Delta value for space allocated |
| |
| Cumulative value for table scans |
| |
| Delta value for table scans |
顺便说一句DBA_HIST_TBSPC_SPACE_USAGE视图可以监控表空间的使用趋势
感谢杨帅军的指点
参考至:http://oracle.erkansaka.org/2007/09/how-to-determine-tables-with-highest.html
http://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3165.htm
本文原创,转载请注明出处、作者
如有错误,欢迎指正