My Oracle Support Banner

Duplicate Record Even After Retention Time Of Duplicate Check EP Node (Doc ID 2767004.1)

Last updated on APRIL 11, 2021

Applies to:

Oracle Communications Offline Mediation Controller - Version 12.0.0.1.0 and later
Information in this document applies to any platform.

Symptoms

When a same already processed Call Data Record(CDR) is passed after the partition retention time and duplicate check file deletion, it is getting rejected as duplicate record instead of creating a new partition with the key and processing the CDR

For example:
- Start time :20200724133300 (13:33 CET) (11:33 GMT)
- Duration: 60 sec (End time calculates as 20200724133400)
- Partition file creates with GMT time 2020-07-24T11-00-00.000_2020-07-24T12-00-00.000.db (from 11:00 GMT to 12 GMT)
- Get file deleted after 1 hour from the end time of the file 13:00 GMT(15:00 CET)
Getting as duplicate even after the retention time
 



STEPS
------------
The issue can be reproduced at will with the following steps:

  1. Within retention period, CDR with the same timestamp and MSISDN but different other values of session id is processed successfully as it probably checks for partition duplicate key.
  2.  After retention period, passing same CDR which got rejected as duplicate within retention period by changing only timestamp got processed successfully.
  3.  After retention period, CDR with only same timestamp and same Mobile Station International Subscriber Directory Number(MSISDN) got rejected as duplicate or too old, in this case session id(duplicate key) would be different as the other values that add up to session id are different.
  4.  After retention period, CDR with only same timestamp and different MSISDN got rejected as duplicate or too old, in this case session id(duplicate key) would be different as the other values that add up to session id are different.

    In conclusion, Timestamp is stored somewhere in the OCOMC memory even after retention period which rejects it as duplicate or too old record.

    Expected output: As part of this fix, get the info message after retention as too old for same timestamp CDRs instead of sending as duplicate without any info message.



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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