Leak of DB Sessions And Memory In Pipeline With Duplicate Check Enabled
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]
Information in this document applies to any platform.
Bug <<6901909>> was not propagated from BRM V7.2 to BRM V7.3. This bug (DUPLICATE CHECK SEMAPHORE DOES NOT 'CLEANUP' CORRECTLY) affected consumption of DB sessions and memory in case of duplicate checks.
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