Delay In Updating Of ECE Cache After Product Cancellation
(Doc ID 2621711.1)
Last updated on DECEMBER 23, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Performed a full stop and start of Elastic Charge Engine (ECE) servers @ 12th Dec, 2019 early morning, it was observed that product cancellation related counter update in ECE was delayed significantly.
Following is the flow:
1) Policy And Charging Rules Function (PCRF), Sy Spending-Limit-Report-Request (SLR) Initial @10:01:33 BRT
--> Returned with counter KBU
2) Product cancellation in Billing And Revenue Management ()BRM @10:01:48 BRT
3) PCRF. Sy Intermediate @10:01:56 BRT
--> Returned with 4 counters
a) Expected: 3 counters (OOB, KBU & BONUSA)
b) Actual response: 4 counters (OOB, KBU, KBU & BONUSA)
e.g. in diameter.log
10:02:14 BRT --> Returned with 4 counters (with duplicate KBU counters)
10:46:09 BRT --> Returned with 4 counters (with duplicate KBU counters)
17:33:21 BRT --> Returned with 3 counters --> Session established and traffic started
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document