My Oracle Support Banner

ECE CDRStore and CDRFormatter Performance Improvement (Doc ID 2880668.1)

Last updated on MAY 15, 2024

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Goal

On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.4.0 version, Cloud Native Deployment (CNE)

it is observed that CDRStore is deployed with no index and injection rate of 250 Call Detail Records (CDRs)/second leaves 500k rows in the CDRStore table. This table was deployed in the ECE_DATA tablespace with no index.

Improvements Needed:

Customer need multiple delete treads, and also they need how to control and increase not just the number of select and delete treads, but also how to control the number of rows being selected and deleted

1. They need to be able to control/increase the "select" and "delete" treads
2. They need to be able to control/increase the number of rows being selected and deleted (example 20 rows instead of just 1)

Ideally they want ,

at least 10 treads on the select with 25 row array fetch
at least 10 treads on teh delete with 25 row array fetch
 

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.