Suspended CDR Due To Service Login Not Updated In Pipeline Memory
Last updated on NOVEMBER 25, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.1 to 7.5.0]
Information in this document applies to any platform.
1. CDRs (usage records) are suspended for some of the accounts in production due to un-synchronized data between BRM and pipeline.
2. This issue has been observed for some time already, though the number of impacted accounts are not significant. Averagely, 106 out of 1996 accounts (~5%) created are not updated in pipeline.
3. The workaround that has been identified is to restart the pipeline, which will actually synch over BRM data to the pipeline memory.
This is causing approximately 700 CDR fallout per day, which will potentially result in revenue loss to the client if we do not restart the pipeline on a recurring basis.
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