AWR数据增长较快,导致sysaux表空间使用较高

SQL> select f.tablespace_name,
2 a.total,
3 f.free,
4 round((f.free / a.total) * 100) "% Free"
5 from (select tablespace_name, sum(bytes / (1024 * 1024)) total
6 from dba_data_files
7 group by tablespace_name) a,
8 (select tablespace_name, round(sum(bytes / (1024 * 1024))) free
9 from dba_free_space
10 group by tablespace_name) f
11 WHERE a.tablespace_name = f.tablespace_name(+)
12 order by "% Free"
13 / TABLESPACE_NAME TOTAL FREE % Free
------------------------------ ---------- ---------- ----------
UNDOTBS1 5185 6 0
SYSAUX 8660 413 5
USERS 5 4 80
SYSTEM 4640 3798 82
UNDOTBS2 365 335 92
X_DATA 1000 990 99
X_INDEX 1000 986 99

查看是哪些数据库对象占用了sysaux表空间

SQL> select *
2 from (select segment_name,
3 PARTITION_NAME,
4 segment_type,
5 bytes / 1024 / 1024
6 from dba_segments
7 where tablespace_name = 'SYSAUX'
8 order by 4 desc )
9 where rownum <= 20; SEGMENT_NAME PARTITION_NAME SEGMENT_TYPE BYTES/1024/1024
------------------------------ ------------------------------ ------------------ ---------------
WRH$_EVENT_HISTOGRAM_PK WRH$_EVENT__1402125233_0 INDEX PARTITION 736
WRH$_EVENT_HISTOGRAM WRH$_EVENT__1402125233_0 TABLE PARTITION 658
WRH$_LATCH WRH$_LATCH_1402125233_0 TABLE PARTITION 588
WRH$_SQLSTAT WRH$_SQLSTA_1402125233_0 TABLE PARTITION 560
WRH$_SYSSTAT_PK WRH$_SYSSTA_1402125233_0 INDEX PARTITION 504
WRH$_LATCH_PK WRH$_LATCH_1402125233_0 INDEX PARTITION 440
WRH$_SYSSTAT WRH$_SYSSTA_1402125233_0 TABLE PARTITION 368
WRH$_PARAMETER_PK WRH$_PARAME_1402125233_0 INDEX PARTITION 336
WRH$_PARAMETER WRH$_PARAME_1402125233_0 TABLE PARTITION 280
WRH$_LATCH_MISSES_SUMMARY_PK WRH$_LATCH__1402125233_0 INDEX PARTITION 280
WRH$_SEG_STAT WRH$_SEG_ST_1402125233_0 TABLE PARTITION 256
WRH$_SYSTEM_EVENT WRH$_SYSTEM_1402125233_0 TABLE PARTITION 232
WRH$_LATCH_MISSES_SUMMARY WRH$_LATCH__1402125233_0 TABLE PARTITION 224
WRH$_SYSTEM_EVENT_PK WRH$_SYSTEM_1402125233_0 INDEX PARTITION 216
WRH$_SQLSTAT_PK WRH$_SQLSTA_1402125233_0 INDEX PARTITION 160
WRH$_SERVICE_STAT_PK WRH$_SERVIC_1402125233_0 INDEX PARTITION 152
WRH$_DLM_MISC WRH$_DLM_MI_1402125233_0 TABLE PARTITION 120
WRH$_ACTIVE_SESSION_HISTORY WRH$_ACTIVE_1402125233_0 TABLE PARTITION 120
WRH$_SQLSTAT_INDEX WRH$_SQLSTA_1402125233_0 INDEX PARTITION 112
WRH$_SEG_STAT_PK WRH$_SEG_ST_1402125233_0 INDEX PARTITION 104

查看awr快照保留期限。设置的期限是8天,但是真正保留了258天

SQL> select sysdate - a.sample_time ash,
2 sysdate - s.begin_interval_time snap,
3 c.RETENTION
4 from sys.wrm$_wr_control c,
5 (select db.dbid, min(w.sample_time) sample_time
6 from sys.v_$database db, sys.Wrh$_active_session_history w
7 where w.dbid = db.dbid
8 group by db.dbid) a,
9 (select db.dbid, min(r.begin_interval_time) begin_interval_time
10 from sys.v_$database db, sys.wrm$_snapshot r
11 where r.dbid = db.dbid
12 group by db.dbid) s
13 where a.dbid = s.dbid
14 and c.dbid = a.dbid; ASH SNAP RETENTION
---------------------------------------- ---------------------------------------- -------------------------------------
+000000258 08:55:03.824 +000000008 08:55:30.192 +00008 00:00:00.0

也可以通过dba_hist_snapshot和WRH$_EVENT_HISTOGRAM进行比较

SQL> select min(snap_id),MAX(snap_id) from dba_hist_snapshot;

MIN(SNAP_ID) MAX(SNAP_ID)
------------ ------------
5489 6350 SQL> select min(snap_id),MAX(snap_id) from WRH$_EVENT_HISTOGRAM; MIN(SNAP_ID) MAX(SNAP_ID)
------------ ------------
168 6350 SQL>

通过MOS查看,这是数据库的一个bug:

  Document 14084247.8 Bug 14084247 - Failed AWR purge can lead to continued SYSAUX space use

因为purge操作失败,split分区表没有成功。所以导致分区大小不断增加,进而影响性能(purge job超时,导致AWR过期数据没有被清空)。

但是,即使是安装了补丁后,也不是立即生效,可能需要等一段时间才能生效。

安装了补丁后,还要按照以下步骤执行purge操作:

1) drop expired partitions (DDL)

2) purge by callback (anything can happen here, but mostly no-ops or regular DELETE operations)

3) purge regular non-partitioned tables (i.e, DELETE)

4) split partitions (DDL)

Excessive AWR Growth From Partitioned Objects Such as SYS.WRH$_EVENT_HISTOGRAM Causing Sysaux to Grow的更多相关文章

  1. ORA-04089: cannot create triggers on objects owned by SYS

    04089 问题原因 因为你在以sys用户创建触发器,但oracle却不建议在sys用户下创建触发器.

  2. Oracle Tuning 基础概述01 - Oracle 常见等待事件

    对Oracle数据库整体性能的优化,首先要关注的是在有性能问题时数据库排名前几位等待事件是哪些.Oracle等待事件众多,随着版本的升级,数量还在不断增加,可以通过v$event_name查到当前数据 ...

  3. How to Resize a Datafile (文档 ID 1029252.6)

    APPLIES TO: Oracle Database - Enterprise Edition - Version 9.2.0.1 and laterInformation in this docu ...

  4. Golang源码探索(三) GC的实现原理

    Golang从1.5开始引入了三色GC, 经过多次改进, 当前的1.9版本的GC停顿时间已经可以做到极短. 停顿时间的减少意味着"最大响应时间"的缩短, 这也让go更适合编写网络服 ...

  5. Golang源码探索(三) GC的实现原理(转)

    Golang从1.5开始引入了三色GC, 经过多次改进, 当前的1.9版本的GC停顿时间已经可以做到极短.停顿时间的减少意味着"最大响应时间"的缩短, 这也让go更适合编写网络服务 ...

  6. golang----GC的实现原理

    Golang从1.5开始引入了三色GC, 经过多次改进, 当前的1.9版本的GC停顿时间已经可以做到极短.停顿时间的减少意味着"最大响应时间"的缩短, 这也让go更适合编写网络服务 ...

  7. What is Scalability?

    Scalability is a system's ability to process more workload, with a proportional increase in system r ...

  8. FAQ – Automatic Undo Management (AUM) / System Managed Undo (SMU) (Doc ID 461480.1)

    FAQ – Automatic Undo Management (AUM) / System Managed Undo (SMU) (Doc ID 461480.1) APPLIES TO: Orac ...

  9. Go内存管理一文足矣

    最早学习C.C++语言时,它们都是把内存的管理全部交给开发者,这种方式最灵活但是也最容易出问题,对人员要求极高:后来出现的一些高级语言像Java.JavaScript.C#.Go,都有语言自身解决了内 ...

随机推荐

  1. 【转载】存储scale-up和scalce-out架构

    转自:存储scale-up和scalce-out架构 存储scale-up和scalce-out架构 Scale-up,即纵向扩展架构.从下面的拓扑图我们可见,纵向扩展是利用现有的存储系统,通过不断增 ...

  2. MyBatis之传入参数

    在MyBatis的select.insert.update.delete这些元素中都提到了parameterType这个属性.MyBatis现在可以使用的parameterType有基本数据类型和Ja ...

  3. A20VGA和lvds显示的切换-

    ./fex2bin sys_config_lvds.fex /boot/script.bin sys_config_lvds.fex的作用:配置各种外设,端口,I/O针脚信息的文件 生成 script ...

  4. Centos下使用Heartbeat实现集群[转]

    Linux 包括 CentOS 下高可用性(HA:High Availability)集群方案很多,而 Heartbeat 是比较常见和性价比比较高的一种。一、硬件及网络连接 群集一般需要2台以上服务 ...

  5. AES加密时抛出 Illegal key size or default parameters

    使用AES加密时,当密钥大于128时,代码会抛出java.security.InvalidKeyException: Illegal key size or default parameters Il ...

  6. struct stat结构体的详解和用法

    [cpp] view plaincopy //! 需要包含de头文件 #include <sys/types.h> #include <sys/stat.h> S_ISLNK( ...

  7. DefaultHttpClient使用

    转自:http://username2.iteye.com/blog/1664995 博客分类:  java 工具类 javaio  ]; } json = JSONObject.fromObject ...

  8. error: jump to label ‘XXXX’ [-fpermissive]

    http://www.cnblogs.com/foohack/p/4090124.html 下面的类似的源码在MSVC上能正确编译通过.但是gcc/g++上就会错: 1. if(expr)2. got ...

  9. SDP协议中的Continuation State

    在SDP request和SDP response中,最后一部分为Continuation State,结构如下: 它用于一次response不够把所有的Data传回去的情况.这时候需要将respon ...

  10. HBase的二级索引,以及phoenix的安装(需再做一次)

    一:HBase的二级索引 1.讲解 uid+ts 11111_20161126111111:查询某一uid的某一个时间段内的数据 查询某一时间段内所有用户的数据:按照时间 索引表 rowkey:ts+ ...