My Oracle Support Banner

Infodom Data Source Missing When Starting Weblogic for OFSAA Deployment (Doc ID 2592139.1)

Last updated on MARCH 03, 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)


In a new OFSAA environment, when starting Weblogic, reviewing the messages in the nohup.out or AdminServer.log, there are no references to the Data Source created for the Infodom.

There are references to the FICMASTER Data Source.  For example:

####<Jun 27, 2019 2:02:01 PM EDT> <Info> <JDBC> <> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1561658521383> <BEA-001174> <Creating data source named FICMASTER, JNDI Name = jdbc/FICMASTER.>
####<Jun 27, 2019 2:02:01 PM EDT> <Info> <JDBC> <> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1561658521442> <BEA-001512> <Data source FICMASTER has been successfully created.>

But similar entries are missing for the Infodom data source.

You can log into OFSAA successfully.  However, you find the following error in the web layer's FUSIONSUBSYSTEMSService.log:

javax.naming.NameNotFoundException: Unable to resolve 'jdbc.<INFODOM>'. Resolved 'jdbc'; remaining name '<INFODOM>'
       at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(
       at weblogic.jndi.internal.BasicNamingNode.lookupHere(
       at weblogic.jndi.internal.ServerNamingNode.lookupHere(
       at weblogic.jndi.internal.BasicNamingNode.lookup(
       at weblogic.jndi.internal.BasicNamingNode.lookup(
       at weblogic.jndi.internal.WLEventContextImpl.lookup(
       at weblogic.jndi.internal.WLContextImpl.lookup(
       at javax.naming.InitialContext.lookup(

In the Weblogic Administration console, in Data Sources, an entry is created for the <INFODOM> which looks correct.  As a result, you do not know what is causing this issue.


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

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