Last updated on MAY 25, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Pipeline Manager
The user has constantly getting CDR processing throughput of around 3 million per hour, but the throughput has suddenly degraded severely and dropped down to around 300K per hour.
There were no errors in the log and no long running sessions in the database or from the AWR report.
With instrumentation enabled, it is noticed that the time was being taken in the customer search module when the accounts were not in the memory initially. Once new CDRs have being reprocessed for accounts which were already present in the memory, the processing was very quick. However, for accounts which were probably not in the memory, the processing was very slow.
Initial loading was set to false in the Pipeline registry.
The count of records of main tables are:
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