57223, 619 PM Document Display Copyright(c) 2023, race Al rights reserved, Oracle Confident How to Manuall 2536631.1) In this Document ‘Symptoms Changes Cause Solution Oracle Database - Enterprise Edition - Version 11.2.0.4 and later Information in this document applies to any platform. The AWRINFO.sq| output shows High Space Usage attributed by Occupant "SM/AWR" Purge Orphan Rows from AWR Repository Tables In Sysaux Tablespace (Doc ID Snippet of the AWRINFO Output HHEHRREEAHAEREEEREERARERERAEEERE EE RRERERHEREEERETAE EEE (1) AWR Snapshots Information HHEHRRERAEHEREEER EE RAR ER ERAEE ERE RERAREREEHERERE ERATE EEE (1a) SYSAUX usage - Schema breakdown (dba_segments) | | Total SYSAUX size 795,615 MB ( 86% of 925,096.0 MB MAX with AUTOEXTEND OFF ) | | Schema SYS occupies 795,615 MB ( 99.9% ) (1b) SYSAUX occupants space usage (v$sysaux_occupants) [Occupant Name Schema Name Space Usage | - . | SM/OPTSTAT sys 40,960 MB | SM/AWR SYS 614,400 MB (3b) Space usage within AWR Components (> 500K) COMPONENT MB SEGMENT_NAME - % SPACE_USED SEGMENT_TYPE FIXED 204,800.0 WRH$_SYSMETRIC_HISTORY + 99% TABLE FIXED 102,400.0 WRH§_SYSMETRIC_HISTORY_INDEX + 84% INDEX hitpsseupport oracle, comlepmesitaces/SearchDocDisplay?_adlct-slate=enpp2ycwt_4#CAUSE 157223, 619 PM Document Display FIXED 51,200.0 WRHS_SYSMETRIC_SUMMARY = 98% TABLE FIXED 25,600.0 WRHS_RSRC_CONSUMER_GROUP. = 90% TABLE FIXED v0.0 WRM§_SNAPSHOT_DETAILS INDEX - 70% INDEX FIXED v0.0 WRH$_SYSMETRIC_SUMMARY_INDEX - 81% INDEX FIXED v0.0 WRM§_SNAPSHOT_DETAILS + 98% TABLE FIXED v0.0 WRH$_MUTEX_SLEEP_PK ~ 82% INDEX MMON Auto Purging fails during the Purging process Many reasons could be a Possible cause for the failure during the purging process Database slowness with the spike in OS resources (CPU/10 Contention) Database Hang MMON purging itself takes more time to complete and it eventually fails with the Error Message “ORA-12751: CPU time or run time policy violation" + MMON suspension and not active ‘+ MMON will not Purge any ORPHAN Rows during Future purging Process. It has to be Manually Deleted. Below steps can be used to Manually Purge ‘+ Check the Size of the SM/AWR and its Associated Tables in the section "(3b) Space usage within AWR, Components (> 500K)" of the AWRINFO.sql output ‘+ If the Size of the Objects referenced in the above Section are of Huge Size, then try the below Manual Purging Approach + In this Example we will use the Object Name : WRH$_SYSMETRIC_HISTORY and how to find the existence of ORPHAN Rows and Manual Purging STEP 1: Find out the ORPHAN ROWS exists using the below Script: ~ If the Output > 0, then it is confirmed Orphan Rows exists ~ If the Output = 0, then NO Orphan Rows Exists: SELECT MIN(SNAP_ID), MAX(SNAP_ID), COUNT (*) FROM SYS.WRIS_SYSMETRIC HISTORY A WHERE NOT EXISTS (SELECT * FROM SYS.DBA_HIST SNAPSHOT B WHERE B.SNAP_ID = A.SNAP_ID AND A,DBID = B.DBID); Below script output will show the CURRENT MIN and MAX SNAP_ID exists in DBA_HIST_SNAPSHOT SELECT MIN(SNAP_=D), MAX(SNAP_ID), COUNT (+ SNAPSHOT? STEP 2: Before Purging shut-off the AWR Snapshot Collection temporarily using the below command : :XEC DBMS_WORKLOAD_REPOSITORY .MODIFY_SNAPSHOT_SETTINGS (INTERVAL => 0); hitpsseupport oracle, comlepmesifaces/SearchDocDisplay?_adlct-slate=enpp2ycwt_4#CAUSE 2857223, 619 PM Document Display STEP 3: Check the Number of Rows to be Retained matching the CURRENT SNAP_ID's : SELECT COUNT(*) FROM SYS.WRHS_SYSMETRIC_ETSTORY (DBID, SNAP_ID) IN (SELECT DBID,SNA?_ID FROM DEA_HIST_SNAPSHOT) ; Create a Backup Table to Store all the Rows matching to Current Snap-Ids SELECT * PROM SYS.WRIS_S {C_HISTORY WHERE (DBID,SNAP_T3) IN (SELECT DS2D,SNAP_ID FROM DBA_HIST_SNAPSHO! Cross Check the Count of Rows in the Back-up Table matches to the First Script Output in "Step 3” SELECT COUNT(*) FROM SYS.WRHS_SYSMETRIC_HISTORY_BACKUP; STEP 4: ‘Truncate the Main Table , example : SYS.WRH$_SYSMETRIC_HISTORY and INSERT (using Direct Path) the Rows to be retained from the Back up Table and Commit INSERT /*+ APPEND */ TNTO SYS.WRHS SYSMETRIC HTSTORY St SYS.WRHS_SYSMETRIC_HTSTORY_BACKUP: cowirT; Restore AWR snapshot collection: INTERVAL ~> 60) STEP 6: Drop the Backup Table which was created to Retain the Matching Rows: DROP TABLE SYS.WRHS_SYSMETRIC NOTE: ‘The above steps can be performed without a DB restart, but AWR Snapshot Collection should be shut off during the Manual Purging, Preferably during the Maintenance Window ‘The above steps can be used for Other Top Tables referenced in the Section "(3b) Space usage Components (> 500K)" Once the Purging is Done for the Tables, the Space Used by the respective Table-Indexes will also be released AWR Dida fine what you are looking for? tps:support oracle, comlopmosifaces/SearchDocDisplay?_adl ct stat pp2yewr_4#CAUSE 3