My Oracle Support Banner

All CDRs Processed Via OCOMC are not Loaded to EVENT_T Table in BRM (Doc ID 2951858.1)

Last updated on JULY 21, 2023

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
It is observed that all the Call Detail Records (CDR) which were processed by Oracle Communications Offline Mediation Controller (OCOMC) are not loaded to Billing and Revenue Management (BRM) EVENT_T table.
There are many ".error" files generated in the input folder of Collection Cartridges (CC) node which are not loaded in EVENT_T table. 

In step 8 below, balance got updated in Elastic Charging Engine (ECE) for both customers, but the balance in BRM got updated for only one customer as the out file was not processed.

STEPS
--------------
1. Create two events EventDealayedSessionTelcoGsm (/gsm) and EventDelayedSessionTeloc5gGsm (/5g/gsm).
2. Set below configurations for Rated Event Manager (REM) and ensure it is running in the BRM server.
           pluginPath="brm-rated-event-manager-12.0.0.4.0.jar"
           pluginType="com.oracle.brm.ref_brm_plugin.RatedEventManagerCdrPlugin"
           refMode: DIRECT,
           remEnabled:true
3. Set threadpoolSize as 1 and checkPointInterval 30 seconds.
4. Update other Rated Event Formatter (REF) properties according to database configuration.
5. Set threadpoolsize as 1(through jconsole) for REF and restart REF.
6. Create a customer for each event.
7. Send usage for both of them.
8. Validate the balance and filenames in logs.

Cause

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
Symptoms
Cause
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.