Messageserver Fails with 'Unable to Connect to the Config Database' Using Wrong Database Name (Doc ID 2193996.1)

Last updated on NOVEMBER 20, 2024

Applies to:

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA), the messageserver is not starting.

When you try to start the messageserver using agentstartup.sh, the following error is output to the nohup.out:

[AESCryptorImpl.handleJVM]->INFO:JVM created successfully...
FAILED: create_oci_session() - error attaching to server using OCIServerAttach()...
FAILED: log_on().
OCIERROR: ORA-12154: TNS:could not resolve the connect identifier specified

CI18NProvider::CI18NProvider, Error, unable to connect to the config database
CI18NProvider::CI18NProvider, Error, generic exception while trying to construct an instance of I18NProvider
ClsUSmsConnect::ClsUSmsConnect(), Error, a generic exception was caught while trying to initializing the class
[14-11-24 09:09:07 GMT AM][INFO][BACKEND][OFSAA][MESSAGESERVER_LOG_TRACE_XXXXX] ConnectToDatabase, connecting config DB with <config user> @ <Database SID>
FAILED: create_oci_session() - error attaching to server using OCIServerAttach()...
FAILED: log_on().
OCIERROR: ORA-12154: TNS:could not resolve the connect identifier specified

[14-11-24 09:09:07 GMT AM][SEVERE][BACKEND][OFSAA][MESSAGESERVER_LOG_TRACE_XXXXX] ConnectToDatabase: FatalError, could not connect to the DB server using
FAILED: - error closing the session using OCISessionEnd()...
[14-11-24 09:09:07 GMT AM][SEVERE][BACKEND][OFSAA][MESSAGESERVER_LOG_TRACE_XXXXX] Could not start Message Logger Server ...

The error message contains the wrong Database SID value.  The router and am processes start successfully.

Cause

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