My Oracle Support Banner

ECM: Batch Performance Issues AccountHousehold Summary (Doc ID 2918194.1)

Last updated on JANUARY 02, 2023

Applies to:

Oracle Financial Services Enterprise Case Management - Version 8.0.7 and later
Information in this document applies to any platform.

Goal

As part of our analysis we need to partition and purge the below given 4 tables.
FCC_ACCOUNTBALANCESMRY_LOOKUP
FCC_HOUSEHOLDSMRY_LOOKUP
FCC_ACCT_SMRY_MNTH
FCC_HH_SMRY_MNTH


However while we do so there is comparion done with mantas datamodel. In mantas we have 14 and 25 partitions maintained for these source tables.
OWNER TABLE_NAME PARTITIONING_TYPE PARTITION_COUNT PARTN_TYPE_CD PARTITION_TYPE
MANTAS HH_SMRY_MNTH RANGE 14 M Monthly
MANTAS ACCT_SMRY_MNTH RANGE 25 M Monthly

The question here is on purging the data in ECM,
Option1) should compare mantas table to ECM table and retain similar partition exactly, in short delete all other partition data in ECM which doesn't exists in mantas. Ideally maintain same 14 months and 25 months of data in ECM as well.

Option2) Do we have to do conditional delete for these 4 tables, considering the lookup tables are used in corresponding evented tables as well?
FCC_ACCOUNTBALANCESMRY_LOOKUP
FCC_ACCT_SMRY_MNTH
FCC_HOUSEHOLDSMRY_LOOKUP
FCC_HH_SMRY_MNTH

which option should we take and why?
Is there a relevance to hold old partition data just because it already got loaded in system in evented tables?
Can we just go ahead and straight away delete partition data which doesn't exists in mantas?

which approach is better approach?
 

Solution

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
Goal
Solution


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