javax.naming.NameNotFoundException: Unable to resolve 'jdbc.OIADataSource'. Resolved 'jdbc' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'jdbc.OIADataSource'. Resolved 'jdbc']; remaining name 'OIADataSource'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.OIADataSource'. Resolved 'jdbc'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)

Even though I have the following snippet of code which shows the correct JNDI value of jdbc/OIADatasource...

DataSource ds = null;
try {
ds = (javax.sql.DataSource) context.lookup("jdbc/OIADataSource");
} catch (NamingException e) {
e.printStackTrace();
}

Assuming you've checked that the JNDI is correct, it is likely to be unavailable, possibly due to the fact that the data source is not assigned to any particular Weblogic server (either to the weblogic admin or one of the managed servers).

Log into the Weblogic domai and on the left side within the domain structure, Expand out the services and select data sources. Select the datasource that you have created in the past, which has all the database connections available.

Within the Targets tab, select the server you want to use. In this example, when the AdminServer starts, so will the availability of the data source. Select save and bounce the Weblogic server.

About the author