ALM Process Gets Stuck in Ongoing with 'Signal number = 9'
Last updated on DECEMBER 16, 2016
Applies to:Oracle Financial Services Asset Liability Management - Version 5.6 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Asset Liability Management (ALM) 5.6, an ALM Process gets stuck in the 'Ongoing' status. The last SQL in the ofsrm.xxxxxx.log from $FIC_DB_HOME/log/FusionApps in the following:
Module Logging OFS Access module data: insert
insert into FSI_PROCESS_ERRORS(process_sys_id, id_number,
sequences, field_name, field_value, corrected_value,
default_value, severity, error_date, error_time, table_name,
error_description, error_code, num, leaf_num_id, leaf_node, sim,
values (:process_sys_id, :id_number, :sequences, :field_name,
:field_value, :corrected_value, :default_value, :severity,
:error_date, :error_time, :table_name, :error_description,
:error_code, :num, :leaf_num_id, :leaf_node, :sim, :batch_run_id
Module Logging OFS calculation module data: Child exited with return status 0, Child Status 1
Additionally, a Signal number 9 (Signal 9) error exists in the am_log_file.log from $FIC_DB_HOME/log:
2016-11-15 | 18:23:44 | AM | SEVERE | | | GetChildStatus : Child Terminated abnormally. Signal number = 9
2016-11-15 | 18:23:44 | AM | SEVERE | | | Sigchild Handler : Child process Returned failure
As a result, you cannot get the required output from the ALM Process.
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