Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0]
Oracle Solaris on SPARC (64-bit)
Sun Solaris SPARC (64-bit)
***Checked for relevance on 12-Jun-2014***
Application Servers running the billing processes, are experiencing lack of memory due to the seizing of memory which appears never released by the user processes. It is noticed that the memory consumption increases when the traffic (phone calls) raises, decreases when the traffic lowers and stops during the night (no traffic offered to the billing application). So it is necessary to restart the CM twice a day to release the memory resources before the application get stuck.
From further analysis it is observed that the memory consumption of CM master process is always constant so no leakage on that front. With a restart, the CM master process is basically restarted and other child processes are killed. As far as the child process leakage is concerned some possible leak is observed in fm_rate_utils_set_rating_result which might have caused the above problem when the traffic volume is very high.
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