Excessive Debug Statements Output to Nohup.out When Running ALM Processes (Doc ID 1324102.1)

Last updated on JUNE 14, 2011

Applies to:

Oracle Financial Services Asset Liability Management - Version: 5.2.2 and later   [Release: 5 and later ]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

For Oracle Financial Services Asset Liability Management (ALM) 5.2.2, when running an ALM Process that includes a Transfer Pricing rule, you get so many rows output to your $FIC_DB_HOME/bin nohup.out log, the file grows to multiple GB in size.  The nohup.out file contains rows like the following repeated again and again:

wkTP.AccountType100 TmpLeaf110
mTP_Context->wkTP.MethodType: 4
wkTP.AccountType100 TmpLeaf110
mTP_Context->wkTP.MethodType: 4
wkTP.AccountType100 TmpLeaf110
mTP_Context->wkTP.MethodType: 4
wkTP.AccountType100 TmpLeaf110
mTP_Context->wkTP.MethodType: 4

Note: The debug statements are output to the nohup.out file by starting the router, am, and messageserver processes individually from the $FIC_DB_HOME/bin directory (ex. nohup ./router &).

This issue occurs after applying Patch 11060542: "FE430,440 OR INCORRECT FOR 1ST TENOR IN NON-MATURITY BEHAVIOUR PATTERN".

Steps to Reproduce:

1. Start the agent processes individually on the server using the nohup command:

nohup ./router &
nohup ./am &
nohup ./messageserver &

2. Create an ALM Process that includes a Transfer Pricing Rule in "Calculation Elements"
3. Run the ALM Process

The messages above are repeatedly output to the nohup.out file in $FIC_DB_HOME/bin.

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