FTP, PFT, or ALM Processes Fail to Execute with 'Unable to Connect to the Config Database' Error (Doc ID 1942607.1)

Last updated on AUGUST 02, 2017

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 6.1 and later
Oracle Financial Services Profitability Management - Version 6.1 and later
Oracle Financial Services Asset Liability Management - Version 6.1 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), Profitability Management (PFT), or Asset Liability Management (ALM) 6.1, you cannot run the processes successfully.  There are no results and no log files output to $FIC_DB_HOME/logs/FusionApps.

When you run the executables directly on the server as described in <Document 1537000.1> "How to Run Oracle Financial Services Analytical Applications (OFSAA) 6.1 Process via the Command Line", the following errors occur:

Warning: iso88951 does not exist.
Host IP--> xx.x.xx.xx
HostIP... xx.x.xx.xx
Port... xxxx
Connect() failed: -1
MessageLogger::initialize, Fatal Error, unable to connect to message server
MessageLogger Client: Fatal Error, could not initialize the class
[AESCryptorImpl.handleJVM]->INFO: JVM created successfully...
[LOG] Starting up.....
ClsUSmsConnect::ClsUSmsConnect, Forming Login Info statement
FAILED: log_on()
ClsUSmsConnect::retrieveInformation, Error, uanble to connect to the config database
OCI_NO_DATA
Warning : Could not log off 0
ClsUSmsConnect::ClsUSmsConnect, Error, unable to retrive login information: 1
FAILED: log_on()
CI18NProvider::CI18NProvider, Error, unable to connect to the config database
OCI_NO_DATA
Warning : Could not log off 0
CI18NProvider::CI18NProvider, Error, generic exception while trying to construct an instance of I18NProvider
ClsUSmsConnect::ClsUSmsConnect, Error, a generic exception was caught while trying to retriece all information from Single Argument into Constructor


Additionally, the following error exists in the messageserver log file msg_trace_file.log:

[AESCryptorImpl.handleJVM]->INFO: JVM created successfully...
FAILED: log_on()
CI18NProvider::CI18NProvider, Error, unable to connect to the config database
OCI_NO_DATA


These errors appear to cause the processes to fail.

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