PCM_OP_CUST_SET_STATUS Has A Major Memory Leak. (Doc ID 739858.1)

Last updated on JULY 28, 2015

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Problem Statement

The standard opcode PCM_OP_CUST_SET_STATUS (called on the account, not on a service) has a major memory leak.

Steps to Reproduce

Recursively call the set_status opcode for one account and monitor the CM process size grow through another session.

Sample Flist to inactivate account

0 PIN_FLD_POID POID [0] 0.0.0.1 /account 23426297398 0
0 PIN_FLD_PROGRAM_NAME STR [0] "test_memory_leak_cust_set_status"
0 PIN_FLD_END_T TSTAMP [0] (1220392800) Wed Sep 3 00:00:00 2008
0 PIN_FLD_STATUSES ARRAY [0] allocated 20, used 2
1 PIN_FLD_STATUS ENUM [0] 10102
1 PIN_FLD_STATUS_FLAGS INT [0] 64 

 
Sample flist to activate the account:

0 PIN_FLD_POID POID [0] 0.0.0.1 /account 23426297398 0
0 PIN_FLD_PROGRAM_NAME STR [0] "test_memory_leak_cust_set_status"
0 PIN_FLD_END_T TSTAMP [0] (1220392800) Wed Sep 3 00:00:00 2008
0 PIN_FLD_STATUSES ARRAY [0] allocated 20, used 2
1 PIN_FLD_STATUS ENUM [0] 10100
1 PIN_FLD_STATUS_FLAGS INT [0] 64

 Call both these flists in a loop where you keep inactivating and activating the account and observe in another session that the CM keeps growing.

Business Impact

CM memory is growing fast: One as to stop and re-start the CMs frequently, as a consequence, the
system is not available 24 x  7 as it should.


Cause

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