My Oracle Support Banner

ALM Process Hangs with Last Log Statement of 'TM_Context::GetPaymentSchedule' (Doc ID 2724906.1)

Last updated on OCTOBER 17, 2023

Applies to:

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


When running an ALM Process, the process hangs or becomes inactive after processing a certain number of records.  When you check the ALM Cash Flow Engine SQL debug log, the following is the last statement in the log:

Module Logging OFS Access module data: /* 61784512: TM_Context::GetPaymentSchedule */

Note that this message can occur for records with or without a Payment Schedule.

If you run the command "ps -ef|grep ofsrm", you see an inactive Cash Flow engine process on the server.

While the nohup.out from $FIC_DB_HOME/bin shows the process is hanging, there are no specific errors.

There are no rows in FSI_PROCESS_ERRORS and the application server CPU utilization goes to 100 percent


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

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