Processing Pending Files After Restoring ccsCDRLoader Functionality on SMS Cluster

(Doc ID 1277364.1)

Last updated on MARCH 12, 2012

Applies to:

Oracle Communications Network Charging and Control - Version: 2.2.0 and later   [Release: 2.2 and later ]
Information in this document applies to any platform.


The ccsCDRLoader on the SMS (Service Management Server) cluster is configured to load the EDRs (Event Detail Records) into the database. Unfortunately ccsCDRLoader wasn't able to process the EDR as over 20K EDR files piled up in its input directory. That amount of files indicate that ccsCDRLoader doesn't work properly and EDRs' processing has been disrupted. In most cases there won't be any error messages in ccsCDRLoader log file the only symptom is that amount of files won't decrease over time.

To determine the ccsCDRLoader input directory you should find the "ccsCDRLoader" section in
/IN/service_packages/eserv.config file. The parameter which defines the input directory is called "inDir".

In this particular example the content of the eserv.config file is as follows:

ccsCDRLoader = {
  inDir = "/IN/service_packages/CCS/logs/CDR-in"

It means that the input directory for ccsCDRLoader process is /IN/service_packages/CCS/logs/CDR-in. The directory's file count has been checked:

# find /IN/service_packages/CCS/logs/CDR-in -type f | wc -l


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