1

Click here to load reader

Statistics Space Used by SM_OPTSTAT in the SYSAUX Tablespace is Not Reclaimed

Embed Size (px)

DESCRIPTION

Statistics Space Used by SM_OPTSTAT

Citation preview

Page 1: Statistics Space Used by SM_OPTSTAT in the SYSAUX Tablespace is Not Reclaimed

Statistics space used by SM/OPTSTAT in the SYSAUX tablespace is not reclaimedafter purging (Doc ID 454678.1)

In this Document

SymptomsCauseSolution

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.4 [Release 10.1 to 11.2]Information in this document applies to any platform.Oracle Server Enterprise Edition - Version: 10.1.0.4Checked for relevance on 29-Dec-2014

SYMPTOMS

Space used by SM/OPTSTAT in the SYSAUX tablespace can not be reclaimed after purge.

CAUSE

Space is not reclaimed immediately after purge is completed. This is normal behaviour because purge_statssimply deletes data from wri$_optstat* tables with a "delete from ..." statement. Free space will be used fornew inserts into OPTSTAT tables.

SOLUTION

Note: The below solution is recommended to be done in either the least workload time frame (ifinstance can not be shutdown) or in the restricted mode (if instance restart is possible).

Move these tables from the SYSAUX tablespace then return them back again.

-- To implement the solution, please execute the following steps::1- Take a full backup of the database2- Move the tables:

SQL> alter table WRI$_OPTSTAT_TAB_HISTORY move;SQL> alter table WRI$_OPTSTAT_OPR move;SQL> alter table WRI$_OPTSTAT_IND_HISTORY move;SQL> alter table WRI$_OPTSTAT_HISTHEAD_HISTORY move;SQL> alter table WRI$_OPTSTAT_HISTGRM_HISTORY move;SQL> alter table WRI$_OPTSTAT_AUX_HISTORY move;

3- For indexes, find the indexes for the above tables and rebuild them. In case an index is unusable, pleasesee the following example:

Página 1 de 1Document Display

10/12/2015https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=t9vjhrx6e_...