How to Address Issues Where AWR Data Uses Significant Space in the SYSAUX Tablespace
(Doc ID 287679.1)
Last updated on DECEMBER 14, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
- SYSAUX tablespace grows much larger than expected
- Automatic Workload Repository (AWR) is taking a significant amount of space (often 2Gb or more) as seen in the following select:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
Symptoms Cause Solution Fix Known Issues Excessive Retention period Check the retention period is appropriate Set retention period to a shorter duration Segment Advisor has grown too large Determine the largest object in the SYSAUX tablespace Check if AUTOEXTEND is on for the SYSAUX tablespace Check if SYS.WRI$_ADV_OBJECTS is one of the largest objects Check the V$SYSAUX_OCCUPANTS view to see if anything can be moved out of the SYSAUX tablespace Active session history (ASH) has grown too large Check if Active Session History (ASH) takes a large percentage of the total AWR data Delete 'orphaned' Active Session History (ASH) References My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.