FE 210/660 Wrongfully Calculated in Failed Breakage Process Resulting in Core Dump and Signal 11 Errors for Non Maturity Behavior Pattern with Holiday Calendar
(Doc ID 2386924.1)
Last updated on NOVEMBER 14, 2019
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Behavior Pattern (BP)
The selected account had partial breakage i.e. Breakage_type_cd=’2’ and amort_type_cd=’800’ in December’ 16 and ‘700’ in January’ 17.
Breakage process was ran for 31-Jan-2017 and is getting failed with core dump issue in ofstp log.
It was noticed that when the breakage_type_cd=’1’ (i.e. full break) and amrt_type_cd=’800’ in both the months, the process is getting successful.
Module Logging OFS errors: (905002) Child died with signal 11.
Module Logging OFS errors: (905003) Core file renamed to
Running TP, Process ID: 202624
ID_TYPE = 204
Error(Oracle Financial Services Application error) (905002) Child died with signal 11.
Error(Oracle Financial Services Application error) (905003) Core file renamed to core.OFSINFODOM_TASK1_202624_20170131_1.1.
STEPS TO REPRODUCE
1. Create breakage process according to specification.
2. Run it against the provided single account (by use of data filter)
3. Notice the ofstp log errors
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