Identifying Memory Leaks in DM During pin_cycle_forward Execution
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.3.1]
Information in this document applies to any platform.
Qn1: How to analyze memory leaks in DM_Oracle?
Qn2: Usage of memory during pin_cycle_forward execution increase constantly (that's why we suspect a memory leak).
Workaround for this is to kill off pin_cycle_forward process and restarting of BRM (DM-CM) chains.
Is there another way to configure a segmentation of the execution of pin_cycle_forward?
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