How To Handle Suspended Records In Multi-level Pipelines? (Doc ID 1330569.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.1 to 7.3.1.0.1 [Release 7.3.0 to 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 21-Aug-2013***

Goal

In our implementation, there are three layers of pipeline managers. Layer one has DB_ROUTER, layer two has SPLITTER and layer three has Main pipelines for rating (like TAPIN, TAPOUT, HOME_VOICE).
  1. If a CDR fails in layer one due to some error, a suspended CDR is created with status 2
  2. After correcting the data, we recycle the CDR. The CDR now passes the DB_ROUTER. But because of additional errors, the CDR fails in layer three (TAPIN). We now see two suspended CDR in the database, both with status 2
  3. We open the suspense update file using vi editor. We can see the suspense update from DB_ROUTER has status 2 but the suspense update from TAPIN has status 0. This cannot be correct: the CDR should have a single status as follows: When CDR is suspended the status in /suspended_usage is 0, when recycled correctly the status is 2

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