Memory Leaks During Customer Registration and Subscription Purchase
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.1 to 184.108.40.206.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 19-Nov-2010***
1) When a basic customer registration scenario is run several times (creating an account,adding
services and products on this account), the memory analysis tool WDB reports memory leaks that
grow linearly (approximative) with each iteration of this scenario.
2) WDB tool also reports memory leaks during rerating scenarios like backdated deal purchase and backdated deal cancellation in the file fm_rerate_insert_rerate_request.cpp
Steps To Reproduce:
1) Create an account, a subscription service (/service/telco/gsm), a child service
(/service/telco/gsm/telephony), purchase a deal with plan and product on this service.
2) Create an account with a line item on Sept 1st; purchase a back dated GSM telephony product on Sept 7th with a start date of Sept 1st; rate some CDRs; run the billing on Sept 15th; re-rate the above created account on Sept 15th.
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