ALM Process Fails with SIGSEGV Error 'FCSQLTable::FCSQLTable(FCSQLTable const&)+0x0'
(Doc ID 2477644.1)
Last updated on AUGUST 19, 2019
Applies to:Oracle Financial Services Asset Liability Management - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Asset Liability Management (ALM) 8.0.x, when attempting to run any ALM Process, the process fails. There is no error in the ofsrm.xxxxxxx.log from $FIC_DB_HOME/log/FusionApps.
The log ends with the following SQL:
Module Logging OFS calculation module data: select
select distinct a.ALM_COA_ID, a.ISO_CURRENCY_CD
from FSI_D_TERM_DEPOSITS a
where AS_OF_DATE = TO_DATE('10/ 19/ 2018', 'MM/ DD/ YYYY')
order by a.ALM_COA_ID, a.ISO_CURRENCY_CD
This SQL is followed by an "insert into FSI_O_RESULT_MASTER" and then the log ends.
The following error exists when the process is run via command line or in the nohup.out from $FIC_DB_HOME/bin:
ProcSysID = 200506
Running Oracle ALM, Process Rule: 200506 Engine started execution
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007fefc98107d0, pid=8852, tid=0x00007fefcbbf5600
# JRE version: Java(TM) SE Runtime Environment (8.0_141-b15) (build 1.8.0_141-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.141-b15 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libaccess.so+0x277d0] FCSQLTable::FCSQLTable(FCSQLTable const&)+0x0
As a result, no results are output by the ALM Process.
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