My Oracle Support Banner

Question On Duplicate Check Cartridge (Doc ID 1584254.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle Communications Offline Mediation Controller - Version 5.1.1 to 6.0.0 [Release 5.1 to 6.0]
Information in this document applies to any platform.



System was configured with duplicate check for 90 days. Volume of events per day is around 60K. JVM memory is 6GB and OS is running with 64 bit. With this configuration and with the given volume, duplicate check processing time is too high and bringing down the performance.

Currently system is collecting data from two collection cartridges in one node manager. To address this performance issue, we are planning to create two node managers. If we move the collection to new node manager, we need to move the scratch files which hold duplicate keys to new node manager. But, currently the collection ( two collection cartridges) is happening through one one node manager and one duplicate check cartridge, duplicate keys for both data centers were stored in scratch files at one place. Is there anyway to separate the duplicate keys in scratch files corresponding to each collection cartridge?


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

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