Reducing SYSAUX Fragmentation of TABLEs and INDEXes Caused by Statistics Related Activities
(Doc ID 1271178.1)
Last updated on NOVEMBER 09, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
This article discusses SYSAUX fragmentation of TABLEs and INDEXes caused by statistics related activities and links to a procedure to reduce the SYSAUX occupancy by detecting, then reducing the data fragmentation inside the SYSAUX TableSpace.
Certain circumstances can result in the TABLEs and INDEX's that the SYSAUX TableSpace holds being fragmented. Fragmentation means that the data stored is not optimally organized within the TableSpace. This usually happens when data is dynamic, when addition and removal of data cycles happen over time. Examples may include:
- On Oracle Database versions 11.1.0.6/7, in some cases, <Bug 8553944> caused the Oracle Statistics history to be flushed from the SYSAUX tablespace. The data it contains will then grow and might be fragmented.
- If the Oracle Statistics history retention is modified, the amount of data in the tablespace can grow. As a result of this De-fragmentation might be needed.
If we consider the specific case of the SYSAUX TableSpace, this usually happens for the Oracle Statistics related items because
- This data is dynamic as the Oracle Stats are constantly re-calculated
- The amount of history data is growing because of an Oracle bug, see:
<Document 1055547.1> SYSAUX Grows Because Optimizer Stats History is Not Purged
Solution
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
| Goal |
| Solution |
| References |