My Oracle Support Banner

How to Restore Slow ccsCDRLoaders Caused by Backlogged EDRs (Doc ID 2877503.1)

Last updated on JUNE 20, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Goal

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), it is possible for a large backlog of Event Data Records (EDRs) to cause extremely slow ccsCDRLoader throughput.  This can cause a snowball effect of issues where:

1. The number of EDR files on a filesystem suddenly increases
2. This causes the filesystem to slow down as the sheer number of files increases endlessly
3. The ccsCDRLoader falls so far behind that the Charging Control Services (CCS) Partitioning scripts run and make the previous week's tablespace (which is still being written to by ccsCDRLoader) READ ONLY
4. Endless errors are then written to standard out (stdout) and this in turn slows ccsCDRLoader further as it spends a lot of time waiting on filesystem Input/Output (IO)

This article will provide a way to recover from such an outage along with recommendations on how to improve future ccsCDRLoader (and the entire EDR subsystem) performance.

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


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