Memory Corruption Issue During Billing After BRM Upgrade 12 PS4 To PS8 (Doc ID 2987117.1)

Last updated on NOVEMBER 14, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
During the Billing and Revenue Management upgrade process from 12.0 Patch Set (PS) 4 to PS8, the user observes a memory corruption issue specifically in the billing module. The PIN_FLD_OWNER_OBJ is having a junk database (DB) number and the PIN_FLD_PRODUCT_OBJ is storing an incorrect POID number of bal_grp_obj.
The user observes that PIN_FLD_OWNER_OBJ has a junk DB number like "1 PIN_FLD_OWNER_OBJ POID [0] 0.0.2654.54928 /service/custom 117134 0"
Additionally, PIN_FLD_PRODUCT_OBJ is storing an incorrect POID number of bal_grp_obj as in "1 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 115470 0".

When the user runs Valgrind to trace the memory leak, it reported an "Invalid read of size 4" error. The Valgrind output reveals that the issue seems to be originating from the pin_poid_copy function, which is part of the $BRM_HOME/lib/libcmpin.so library. Following that, a chain of functions in different libraries also seems to be contributing to this memory corruption issue.
The output further indicates that the memory address 0x9b193ac is being read after being freed. This is highly indicative of a memory corruption issue.

Following is the snippet of the Valgrind output:

EXPECTED BEHAVIOR
-----------------------
The PIN_FLD_OWNER_OBJ and PIN_FLD_PRODUCT_OBJ fields should have correct and coherent values.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade from PS4 to PS8

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.