PFT 126.96.36.199 Allocation Rule With Static Table Driver Failed With No Error
(Doc ID 2768651.1)
Last updated on APRIL 19, 2021
Applies to:Oracle Financial Services Profitability Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
On PFT 184.108.40.206, Static Table Driver Allocation failed with no error.
When rule is executed, the status is shown as 'Started' in Allocation History. On the rules screen, it's shown as Failure.
The log files are incomplete and there is no error in them. There is no record in fsi_message_log for the respective alloc_sys_id.
Below error was received in console when running the allocation from command-line:
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007f88e7939dec, pid=13897, tid=0x00007f88eaf651c0
# JRE version: Java(TM) SE Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libstdc++.so.6+0xbedec] std::string::assign(std::string const&)+0x2c
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
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