Skip to main content

How to clean SYSAUX Optimizer Statistics History

How to clean SYSAUX Optimizer Statistics History


Many times we come across the SYSAUX tablespace getting full. We can find what is consuming the most space and can clean up.

When new optimizer statistics are collected for a database object, old statistics are sent to SYSAUX tablespace. This information is stored in the "Server Manageability - Optimizer Statistics History" component of SYSAUX tablespace.

This feature is used for DBMS_STATS.RESTORE  procedures.

The default retention for Optimizer Statistics History is 31 days. 
Old information is automatically deleted by Oracle Database, Without any manual intervention based on the retention.

1) Find SYSAUX components and their sizes.
select * from v$sysaux_occupants order by space_usage_kbytes desc;


2)Find biggest segments in SYSAUX
select tablespace_name,owner,segment_name,partition_name,segment_type,trunc((bytes/1024/1024/1024),2) "GB" 
from dba_segments where tablespace_name = 'SYSAUX' order by bytes desc; 

3)Find current retention
select dbms_stats.get_stats_history_retention from dual;

4) Find available stats that have not been purged
select dbms_stats.get_stats_history_availability from dual;

5)Change retention
exec dbms_stats.alter_stats_history_retention(10);

6)Disable retention. (Turn off SYSAUX Optimizer Statistics History feature)
exec dbms_stats.alter_stats_history_retention(0);


7)Completely remove old statistics (the fastest option works as a truncate command)
EXEC DBMS_STATS.PURGE_STATS(DBMS_STATS.PURGE_ALL);

8)Partially remove old statistics
exec DBMS_STATS.PURGE_STATS(SYSDATE-10);

But this will generate huge undo


Show how big the tables are and rebuild after stats have been purged

select sum(bytes/1024/1024) Mb, segment_name,segment_type from dba_segments
where  tablespace_name = 'SYSAUX'
and segment_name like 'WRI$_OPTSTAT%'
and segment_type='TABLE'
group by segment_name,segment_type order by 1 asc;


Show how big the indexes are ready for a rebuild after stats have been purged

select sum(bytes/1024/1024) Mb, segment_name,segment_type from dba_segments
where  tablespace_name = 'SYSAUX'
and segment_name like '%OPT%'
and segment_type='INDEX'
group by segment_name,segment_type order by 1 asc;
/

Note that you cannot enable row movement and shrink the tables as the indexes are function-based

Optional: Rebuild %OPT% tables and indexes in SYSAUX.

1. First check status of all %OPT% indexes. They must be VALID before rebuild.
select  di.index_name,di.index_type,di.status  from  dba_indexes di , dba_tables dt
where  di.tablespace_name = 'SYSAUX' and dt.table_name = di.table_name
and di.table_name like '%OPT%' order by 1 asc;

2. Rebuild tables.
select 'alter table '||segment_name||'  move tablespace SYSAUX parallel 8;' from dba_segments where tablespace_name = 'SYSAUX'
and segment_name like '%OPT%' and segment_type='TABLE';

3. Rebuild indexes.
select 'alter index '||segment_name||'  rebuild online parallel 8;' from dba_segments where tablespace_name = 'SYSAUX'
and segment_name like '%OPT%' and segment_type='INDEX';

4. Find status of all %OPT% indexes. They must be VALID after rebuild.
select  di.index_name,di.index_type,di.status  from  dba_indexes di , dba_tables dt
where  di.tablespace_name = 'SYSAUX' and dt.table_name = di.table_name
and di.table_name like '%OPT%' order by 1 asc;




If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...