Suggestion to Manage/Purge Data for the FW_PUBDATASTORE and PUBSESSION Tables (Doc ID 1916722.1)

Last updated on MAY 31, 2022

Applies to:

Goal

The DBA team is suggesting the following to manage/purge data for the FW_PubDataStore and PubSession tables:
  
 1. Partition the table PubSession on CS_ENDDATE by range, quarterly, or monthly.
 2. Define the FW_PubDataStore.pubsession as foreign key of PubSession.id
 3. Partition the FW_PubDataStore by reference on Pubsession. PubSession.id, i.e. the same way to partition PubSession table.
 4. Purge expired data by dropping expired partitions.
  
With such a partitioning design, you will have data stored in quarterly/monthly partitions. This will make the purging of expired data very simply: just dropping the partitions that you don't want to keep. That can be done without any impact on availability of the table, or causing any fragmentation.

Is this is a supported approach?
 

Solution

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