My Oracle Support Banner

Missing Indexes Causing Poor Performance Of CustomerUpdater (Doc ID 2509759.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.21.0 and later
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.6.0 and later
Information in this document applies to any platform.

Goal

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:

1. AU_GROUP_SHARING_MEMBERS_T.OBJ_ID0
2. PROFILE_SUBSCRIBER_PREFS_T.OBJ_ID0
3. AU_GROUP_T.ACCOUNT_OBJ_ID0
 
Can this be taken as an enhancement request and added to the product ?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.