Cannot Start "am" Server for OFSAA - Call to Bind Failed (Doc ID 1458559.1)

Last updated on JUNE 06, 2024

Applies to:

Symptoms

For Oracle Financial Services Analytical Applications (OFSAA) infrastructure, you cannot start the "am" server when starting all OFSAA server processes.  The following error message exists in the $FIC_DB_HOME/log/am_log_file.log file:

2012-05-14 | 15:57:13 | AM | INFO | | | Thread 4 : Signal Handler Thread Initiated
2012-05-14 | 15:57:13 | AM | INFO | | | Thread 1 : AM_PORT = 6505
2012-05-14 | 15:57:13 | AM | INFO | | | GlobalAccess::Lock_Request : Success
2012-05-14 | 15:57:13 | AM | INFO | | | GlobalAccess::Lock_Reply : Success
2012-05-14 | 15:57:13 | AM | SEVERE | | | SocketServerImpl::Bind : Call to Bind Failed
2012-05-14 | 15:57:13 | AM | SEVERE | | | Thread 1 : Call to Socket Init Failed
2012-05-14 | 15:57:13 | AM | WARN | | | Controller::Set_Shutdown : Shutdown invoked by Thread 1
2012-05-14 | 15:57:13 | AM | SEVERE | | | Thread 1 : Shutdown Initiated - 3

You cannot find an "am" process on the server running the command "ps -ef|grep am".

As a result of this issue, you cannot run Allocation rules, Undo processes, or ALM or FTP process from the interface.

Cause

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