Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
-- Problem Statement:
During processing of large volumes of data, it was noticed that the dm_oracle backends are leaking memory from standard heap memory (not from the shared-memory heap).
-- Steps To Reproduce:
Executing thousands of searches, with the DM configured with the following parameters in the pin.conf file:
- dm nullable_obj_id0_classes /item
- dm nullable_obj_id0_state false
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms