My Oracle Support Banner

Troubleshooting Message Server Errors for OFSAA Infrastructure (Doc ID 1151767.1)

Last updated on FEBRUARY 06, 2023

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI / AAI)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)

Purpose

This document provides troubleshooting steps to help with Message Server errors after new installation of Oracle Financial Services Analytical Applications Infrastructure (OFSAAI).  The message server is required for successful completion of all Financial Services Enterprise Performance Management (EPM) batches.

To check if the message server is running, run the following process status command on the db tier:

$ ps -ef | grep messageserver

The process should appear like the following:

$ ps -ef | grep messageserver
ofsaa    17136     1  0 Jan30 ?        00:14:18 ./messageserver
ofsaa    23674 21890  0 11:58 pts/1    00:00:00 grep --color=auto messageserver

The Message Server is typically started in the Agent script:

cd $FIC_DB_HOME/bin
nohup ./agentstartup.sh &

 

However, it may also be started manually from the $FIC_DB_HOME/bin directory to troubleshoot: ./messageserver.

This document will provide assistance in troubleshooting the following errors:

Could not load program messageserver:
Could not load module /ofsaa51/ofsaai71/ficdb/lib/libDatabase.so.
Dependent module /unix/libclntsh.so could not be loaded.
Could not load module /unix/libclntsh.so.
System error: Not a directory
Could not load module messageserver.
Dependent module /ofsaa51/ofsaai71/ficdb/lib/libDatabase.so could not be loaded.


2010-07-07 | 21:01:50 | messageserver | INFO | | | Log File open successfully
2010-07-07 | 21:01:50 | messageserver | INFO | | | Trying to retrieve Message Server Port ...
2010-07-07 | 21:01:50 | messageserver | INFO | | | ConnectToDatabase, trying to connect to the config DB with USERNAME = <config schema> SID = <SID>
2010-07-07 | 21:01:55 | messageserver | SEVERE | | | ConnectToDatabase: FatalError, could not connect to the DB server using
2010-07-07 | 21:01:55 | messageserver | SEVERE | | | Could not start Message Logger Server ...


MSCONSOLE]ClsULogManager :: Singleton Instance Created
[MSCONSOLE]FAILED: log_on()
[MSCONSOLE]OCI_NO_DATA
[MSCONSOLE]Warning : Could not log off 0
[MSCONSOLE]Going to shutdown console reader now..
[MSCONSOLE]ClsULogManager :: Singleton Instance Created
[MSCONSOLE]FAILED: log_on()
[MSCONSOLE]OCI_NO_DATA
[MSCONSOLE]Warning : Could not log off 0

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Troubleshooting Checklist
 1. Is the correct Oracle client installed?
 2. Has the tnsnames.ora for Oracle been updated with the correct connection information to the OFSAA database?
 3. Confirm all .profile entries for the OFSAA Unix Administrator are correct
References

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