查看AWR各详细使用空间描述

SQL> connect / as sysdba
SQL> @?/rdbms/admin/awrinfo.sql

In this Document
Purpose
Scope and Application
General guidelines for SYSAUX space issues

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.5 to 11.1.0.6
Information in this document applies to any platform.

Purpose

The purpose of this document is to give general guidelines for SYSAUX tablespace space issues to control and decrease the space usage. It refers to several metalink notes for details when necessary.

Scope and Application

This article is intended to help the database administrators to manage space issues in SYSAUX tablespace.

General guidelines for SYSAUX space issues

SYSAUX is a mandatory tablespace in 10g which stores all auxiliary database metadata related to various product options and features. Old data within SYSAUX tablespace is purged accordingly with retention policy and other settings of different components and tablespace shouldn't grow indefinitely. If retention period is set too high or settings to capture data is chosen at detailed level, tablespace can become too large. In this case, space can be reclaimed and growth rate can be controlled with choosing correct retention period and doing some maintenance tasks.

The following sections give a general roadmap for SYSAUX tablespace space issues to identify, control and decrease the space usage. It refers to several metalink notes for details when necessary.

1- Articles for general description of SYSAUX components, space usage and retention

The following articles provide general description of most common SYSAUX components, retention settings, their space usage and corresponding move procedures to reclaim space.

Note Description
Note 329984.1 Usage and Storage Management of SYSAUX tablespace occupants SM/AWR, SM/ADVISOR, SM/OPTSTAT and SM/OTHER Note explains what kind of information is kept by the most common components, such as AWR, OPTSTAT, ADVISOR and OTHER and how to control the contents.
Note:243246.1 10G : SYSAUX Tablespace Note helps to identify the component with the high space usage from V$SYSAUX_OCCUPANTS and to see if there exists a move procedure for the component. If an occupant of the tablespace SYSAUX takes too much space, you can move it to another tablespace and move it back to SYSAUX to reclaim the unused space.
Note 287679.1 Space Management In Sysaux Tablespace with AWR in use Some of the components have no move procedure and some speacial tasks are required to delete old data. Note explains how to change retention period from Grid Control, identify large AWR objects in SYSAUX tablespace, how to delete / cancel old segment advisory data to control and reduce the space usage.

2- Determine AWR objects taking large space.

Script awrinfo.sql can be used to determine the AWR objects taking large space and check awrinfo.sql.


Output is written to awrinfo.lst in the current working directory. Check section (3a) and (3b) in awrinfo.lst is used to find the component and segments with high space usage within AWR.


If space usage is growing steadily for a segment even after retention period is expired and a partition is dropped, then this could be a known problem. You can search for known issues using component and segment name in the report output.

Bug:5974572 is about a similar problem where WRH$_SERVICE_STAT grows indefinitely in RAC environment when there is an application creating and dropping services with dbms_service create_service/delete_service calls repeatedly.

Bug:5974572 WRH$_SERVICE_STAT CAN GROW VERY LARGE ON RAC
Note 427529.1 EXTREME NUMBER OF ROWS ARE ACCUMULATED IN WRH$_SERVICE_STAT

3- If Enterprise Manager (EM, owner:SYSMAN) component takes too much space, you need to follow "Offline Monthly Tasks" to purge the repository tables. Some of the EM components may need to be shutdowned in order to purge the old data. This is documented in Oracle Enterprise Manager manuals and the following is given as a reference for 10.2 Grid Control.

Refer to the following link for details.
Offline Monthly Tasks

[@more@]