Memory Leak On Duplicate Check
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
***Checked for relevance on 08-Aug-2013***
***Checked for relevance on 9-FEB-2015***
There are 5 pipelines, of which one is dedicated to CDRs that are rejected since their respective account has been closed. Therefore users are doing "duplicate check" processing on 4 of these pipelines, which have an important volume of CDRs.
Have discovered that the memory used is going up continuously.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms