Suggestion to Manage/Purge Data for the FW_PUBDATASTORE and PUBSESSION Tables
(Doc ID 1916722.1)
Last updated on OCTOBER 15, 2020
Applies to:Oracle WebCenter Sites - Version 7.6.0 to 126.96.36.199.0 [Release FatWire]
Information in this document applies to any platform.
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?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document