ALM or RM Process Dies With Signal -6 Error (Doc ID 256931.1)

Last updated on MAY 24, 2016

Applies to:

Oracle Risk Manager - Version 4.5 and later
Oracle Financial Services Asset Liability Management - Version 6.1 and later
Information in this document applies to any platform.
Oracle Financial Services Applications (OFSA)
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

You are receiving a Signal -6 error running an ALM process or a 4.5 RM process.

Upon checking the generated ofsrm.XXXXXX log file, you find the following error:

ALM:

Module Logging OFS errors: (905002) Child died with signal 6.

The error occurs after the "select" from the input data table.

Also, in the nohup.out or similar file in $FIC_DB_HOME/bin, the following error exists:

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002ab63197058e, pid=29419, tid=46962125833872
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libcftm.so+0x1a58e] EventGenerator::GetEvent()+0x4e

RM 4.5:

Assertion failed: 0, file procclnt.cpp, line 772

For RM 4.5, after turning off multiprocessing, changing the number of modeling buckets to 1 1 month bucket, and removing all New Business and Prepayment IDs, process still fails with the same error.

Cause

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