My Oracle Support Banner

Pin_rel Crashing with Java OutOfMemoryError Exception when Loading EDRs (Doc ID 2375458.1)

Last updated on OCTOBER 28, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Billing and Revenue Management implemented with Elastic Charging Engine, when using pin_rel (rel_daemon) to load Event Data Records (EDRs) into the Oracle Database, the process is crashing and throwing a Java "Out of Memory" exception.

The following can be seen in the pin_rel log file:

Fri Sep 15 18:47:32 AST 2017
REL running as Daemon = 1
Error encountered in the Database Load Utility: 5001
The following properties key could not be found: 5001
Please update CustomErrorCodes.properties with the appropriate custom error message.
Relinit failed, ThreadId =10
Error encountered in the Database Load Utility: 5001
The following properties key could not be found: 5001
Please update CustomErrorCodes.properties with the appropriate custom error message.
Relinit failed, ThreadId =65445
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x696c2f72, pid=27628, tid=2794122096
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) Server VM (20.1-b02 mixed mode linux-x86 )
# Problematic frame:
# C 0x696c2f72
#
# An error report file with more information is saved as:
# /opt/portal/7.5/apps/pin_rel/hs_err_pid27628.log

 As a result, some EDRs may fail to be loaded.

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.