ALM Process Gets Stuck in Ongoing with 'Signal number = 9' (Doc ID 2206186.1)

Last updated on MARCH 13, 2019

Applies to:

Symptoms

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,
batch_run_id)
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.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.