Last updated on JANUARY 24, 2017
Applies to:Oracle Financial Services Profitability Management - Version 8.0.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
On : 188.8.131.52.4 version, Allocation Entries
When attempting to run Allocation Rules within an Allocation Model, the rules failed inconsistently. When Allocation Rules were run outside the Allocation Model one by one, they are successful.
Program terminated with signal 6, Aborted
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x000000000043baf9, pid=40438, tid=140515576575456
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [ofspa+0x3baf9] TTSCDBMem<IDENTITY, io_identity, IDENTITY_KEY>::TTSCDBMem(int, int, int (*)(void const*, void const*), int, int)+0x3baf9
# Core dump written. Default location: /v02/OFSAA/ficdb/bin/core or core.40438
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x0000000001dae000): JavaThread "main" [_thread_in_native, id=40438, stack(0x00007fffb911b000,0x00007fffb921b000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x000000000000005b
am_log_file.log shows below:
||SEVERE||GetChildStatus : Child Terminated abnormally. Signal number = 6
||SEVERE||Sigchild Handler : Child process Returned failure
1. Run Allocation Model with over 100 rules. Some rules are using FSI_D_MANAGEMENT_LEDGER.
2. There is no pattern for the failure sometimes the model fails after executing 30 rules some times after 10 rules.
3. Allocation Models run individually or within an ICC Batch run in parallel.
3. Allocation Rules were completed successfully outside of the Allocation Model.
4. core files and hs_err_pid got generated.
5. No error in FSI_MESSAGE_LOG or View Log.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms