Expensive Select On SSXAExpiredCacheIds. Can table SSXAExpiredCacheIds be truncated? (Doc ID 2502423.1)

Last updated on SEPTEMBER 20, 2023

Applies to:

Goal

The statement below has an explain plan cost of 140K due to full table scan and order by on the result set:

SELECT dSsxaCacheId, dSsxaCacheType, dSsxaToken, dSsxaTime, dSsxaMessage FROM SSXAExpiredCacheIds WHERE dSsxaCacheType = :"SYS_B_0" ORDER BY dSsxaToken

The table SSXAExpiredCacheIds two weeks ago had about 12M records, and it now has 14M records.

This query is for WebCenter and seems to have been impacted by large document imports.

Can table SSXAExpiredCacheIds be truncated? Can we schedule truncation of this table on quarterly basis? Or is there another method to reduce the size of this table?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.