Splitter Pipeline Performance Issue In Production (Doc ID 1399433.1)

Last updated on JANUARY 01, 2014

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 to 7.2.1.0.1 [Release 7.2.1]
Information in this document applies to any platform.

Goal

Issue :

In a customers production system, the splitter pipeline's performance has degraded from few seconds/CDRs to several minutes/CDRs, which prevents rating process to be executed smoothly.


Details :


Observation :

From the awr reports of the database, it was noticed that the pipeline reads profile data from the database during rating. There are  500K accounts migrated that have the profile object modified lately. After starting pipeline and processing the CDRs, old records are causing pipeline to read older audit profile records. In this context, there is a need to underdtand which field of the au_profile_t table is used by the pipeline in order to verify the validity of the audit record kept in the pipeline memory. We saw that the sql queries are reading effective_t, valid_from_t.

Expectation :

How to address the performance issue ?

Solution

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