Missing Indexes Causing Poor Performance Of CustomerUpdater
(Doc ID 2509759.1)
Last updated on OCTOBER 09, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
During startup of customerUpdater, some missing indexes on BRM tables make customerUpdater sql queries very expensive which makes the startup time of customerUpdater very long and in most cases leading to timeouts and for large databases impossible to synchronize accounts between BRM and ECE.
In order to avoid full table scans by customerUpdater, the following tables & fields should be indexed:
Can this be taken as an enhancement request and added to the product ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document