My Oracle Support Banner

ALM Process Consistently Fails After Log Outputs "Module Logging OFS Access module data: /*interpolation method : 2*/" (Doc ID 2671111.1)

Last updated on MAY 21, 2020

Applies to:

Oracle Financial Services Asset Liability Management - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Asset Liability Management (ALM)

Symptoms

When running an ALM Process, it consistently fails after outputting the following messages to the Cash Flow Engine log (see Document 1683485.1):

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

Module Logging OFS Access module data: /*interpolation method : 2*/

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 errors: (203105) Oracle drv_oci error: Disconnect: Not all ORACLE driver
copies destroyed!

Prior to these messages, there are SQL queries on the Forecast Rates tables (ex. FSI_FCAST_RATES_BUCKETS, FSI_FCAST_IRC_DIRECT_INPUT, FSI_FCAST_IRC_IMP_FORWARD_CHG, etc.)

On IBM AIX, there is a core dump and the following messages are output when running the ALM Process via command line:

| strBatchId : <INFODOM>_<BATCH_NAME>_20191031_2 | strComponentId : Cash Flow Engine | Process ID : 123456 | User ID : <USER> |

ProcSysID = 123456
Running Oracle ALM, Process Rule: 123456 Engine started execution
JVMDUMP039I Processing dump event "abort", detail "" at 2019/11/01 13:53:08 - please wait.
JVMDUMP032I JVM requested System dump using '/ofsaai/ofsaai/ficdb/bin/core.20191101.135308.12451960.0001.dmp' in response to an event
Note: "Enable full CORE dump" in smit is set to FALSE and as a result there will be limited threading information in core file.
JVMDUMP010I System dump written to /ofsaai/ofsaai/ficdb/bin/core.20191101.135308.12451960.0001.dmp
JVMDUMP032I JVM requested Java dump using '/ofsaai/ofsaai/ficdb/bin/javacore.20191101.135308.12451960.0002.txt' in response to an event
JVMDUMP010I Java dump written to /ofsaai/ofsaai/ficdb/bin/javacore.20191101.135308.12451960.0002.txt
JVMDUMP032I JVM requested Snap dump using '/ofsaai/ofsaai/ficdb/bin/Snap.20191101.135308.12451960.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /ofsaai/ofsaai/ficdb/bin/Snap.20191101.135308.12451960.0003.trc
JVMDUMP007I JVM Requesting JIT dump using '/ofsaai/ofsaai/ficdb/bin/jitdump.20191101.135308.12451960.0004.dmp'
JVMDUMP010I JIT dump written to /ofsaai/ofsaai/ficdb/bin/jitdump.20191101.135308.12451960.0004.dmp
JVMDUMP013I Processed dump event "abort", detail "".


You do not know what triggers these errors.

Cause

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
Symptoms
Cause
Solution
References


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