FTP or ALM Process Shows Status of 'Ongoing' in Interface When It Is Complete (Doc ID 1338945.1)

Last updated on FEBRUARY 10, 2017

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.2.6 and later
Oracle Financial Services Asset Liability Management - Version 5.2.2 and later
Oracle Financial Services Funds Transfer Pricing - Version 5.2.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Funds Transfer Pricing (FTP) or Asset Liability Management (ALM), when you run an ALM, FTP or Cash Flow Edits process, you see that the process finishes successfully and outputs results.  However, when you look at the status in the Batch Monitor screen, it lists the process as having a status of "Ongoing".  The status never changes from ongoing to something else like Successful or Failed.

Also, you find the following error message is in the $FIC_APP_HOME/icc/log/iccserver.log file:

[18:09:02,185] - Read from router:
[18:09:02,187] - Parsing router message: ##C##I##H##99.9.99.999##99.9.99.999##RNofstp!!main!!SOFSAAINFOD_200044_EXEC_20110713_4^^Transfer Pricing Engine^^Task1^^20110713^^200044^^OFSUSR^^NULL##
[18:09:02,193] - No of Parameters for the component Transfer Pricing Engine is :5
[18:09:02,193] - Illegal parameter token count. Expecting 5. Received: 7
[18:09:02,203] - Could not interpret router message: ##C##I##H##99.9.99.999##99.9.99.999##RNofstp!!main!!SOFSAAINFOD_200044_EXEC_20110713_4^^Transfer Pricing Engine^^Task1^^20110713^^200044^^OFSUSR^^NULL##
java.lang.IllegalArgumentException: Illegal parameter token count: 7
        at com.iflex.fic.icc.iccal.iccexecution.jobscheduler.message.Message.<init>(Message.java:139)
        at com.iflex.fic.icc.iccal.iccexecution.jobscheduler.message.RouterMessageUtils.interpretReply(RouterMessageUtils.java:118)
        at com.iflex.fic.icc.iccal.iccexecution.jobscheduler.Reader.handleMessage(JobManager.java:385)
        at com.iflex.fic.icc.iccal.iccexecution.jobscheduler.Reader.run(JobManager.java:370)

While this issue does not have an impact on your results, the bad status makes it difficult to determine if a process has ended.

Cause

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