PFT, FTP, or ALM Batch is Stuck in Ongoing Status with ORA-03135 & ORA-03114 (Doc ID 2119285.1)

Last updated on APRIL 24, 2023

Applies to:

Symptoms

In Oracle Financial Services Profitability Management (PFT), Funds Transfer Pricing (FTP), or Asset Liability Management (ALM), a batch has been running for many hours.  For example, a batch of Allocations has been running for 6 hours.  The batch usually completes in 15 minutes.  In the batch, Task4 runs successfully but Task5 has been stuck in the ongoing status for several hours.  No log is created for Task5 in $FIC_DB_HOME/log/FusionApps.

Additionally, the following error exists in the RevAgent.log after Task4 is run:

[AGENTLOG][Reveleus Agent][Sun Mar 06 11:53:35 CST 2016]Activation Manager:Host IP--> xxx.xx.xx.xxx
[AGENTLOG][Reveleus Agent][Sun Mar 06 11:53:35 CST 2016]Activation Manager:HostIP... xxx.xx.xx.xxx
[AGENTLOG][Reveleus Agent][Sun Mar 06 11:53:35 CST 2016]Activation Manager:Port... 6500
[AGENTLOG][Reveleus Agent][Sun Mar 06 11:53:35 CST 2016]Activation Manager:Sigchild Handler : No child for Waitpid - WNOWAIT
[AGENTLOG][Reveleus Agent][Sun Mar 06 15:02:56 CST 2016]Activation Manager:Error Msg :-> ORA-00028: your session has been killed

Another error exists in the MessageServerConsole.log:

[MSCONSOLE]Error Msg :-> ORA-03114: not connected to ORACLE

The error appears to cause Task5 to fail because the Allocation process requires the messageserver process to run successfully.

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.