Memory Leakage in PCM_OP_BILL_UPDATE_JOURNAL (Doc ID 973413.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 to 7.2.1.0.0 [Release 7.2.1]
Information in this document applies to any platform.
***Checked for relevance on 30-Oct-2013***

Symptoms

Memory Leak(MLK) in PCM_OP_BILL_UPDATE_JOURNAL and fm_subs_utils_get_billinfo() causing CM running out of memory at time of pin_bill_accts run.

1) MLK: 2880 bytes leaked in 10 blocks
* This memory was allocated from:
malloc [rtlib.o]
pcmmem_malloc_flisthdr [PcmMemGroup.cpp]
pin_flist_create_with_size [pin_flist.c]
pin_flist_create [pin_flist.c]
PinOwner PinFlist::create() [PinFlist.cpp]
fm_subs_utils_get_billinfo [fm_bill_utils_subs_utils.cpp]
* Block of 288 bytes (10 times); last block at 0xaa7de8

2) MLK: 1600 bytes leaked in 5 blocks
* This memory was allocated from:
malloc [rtlib.o]
pcmmem_malloc_flistflds [PcmMemGroup.cpp]
pini_flist_grow [pcmi.c]
pin_flist_create_with_size [pin_flist.c]
pin_flist_create [pin_flist.c]
pin_license_validate_feature [pin_license.c]
* Block of 320 bytes (5 times); last block at 0xa5b960

MLK: 1600 bytes leaked in 5 blocks
* This memory was allocated from:
malloc [rtlib.o]
pcmmem_malloc_flistflds [PcmMemGroup.cpp]
pini_flist_grow [pcmi.c]
pin_flist_create_with_size [pin_flist.c]
pin_flist_create [pin_flist.c]
op_bill_update_journal [fm_bill_update_journal.c]
* Block of 320 bytes (5 times); last block at 0xa70d58

-- Steps To Reproduce:

Run pin_bill_accts in purify environment.

-- Business Impact:

Due to MLK in opcodes, CM is running out of memory at time of pin_bill_accts run.
This is affecting daily activities like (billing, payment etc).

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