Memory Leaks Observed While Executing PCM_OP_CUST_SET_STATUS
(Doc ID 2466342.1)
Last updated on AUGUST 10, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Memory leaks identified in out of the box opcode PCM_OP_CUST_SET_STATUS using BMT tool (BayMem).
Steps :
1) Created a postpaid account
2) Created service using PCM_OP_CUST_MODIFY_CUSTOMER
3) Changed the status of service from active to close using PCM_OP_CUST_SET_STATUS
4) Detected memory leaks using BMT tool. See below snippet of the report :
EXPECTED BEHAVIOR:
There should be no memory leaks during the execution of opcode PCM_OP_CUST_SET_STATUS.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |