ODI Extend Agent报错_oracle.odi.runtime.agent.invocation.invocationexce-优快云博客

本文链接：https://blog.youkuaiyun.com/qingqingxuelang/article/details/7704633

解决因JNDI名称重复导致的ODI WebLogic Server启动失败问题。通过调整数据源的JNDI名称，确保服务器正常运行。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

在Extend ODI J2EE Agent时,出现了异常但是不影响正常的扩展： CFGFWK-60318: The "JDBC" configuration in your domain is invalid. Try to resolve the issue by clicking Cancel and returning to this section in the wizard. If you cannot resolve the issue, either click Cancel and exit the wizard, or click OK to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

但在启动ODI weblogic Server时，却无法正常启动，查看错误有：

Caused by: oracle.odi.core.exception.OdiRuntimeException: Failed to lookup dataSource from JNDI for name {jdbc/odiMasterRepository}
at oracle.odi.core.datasource.provider.JndiDataSourceProvider.doCreateDataSource(JndiDataSourceProvider.java:58)
at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:98)
... 99 more
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.odiMasterRepository' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/odiMasterRepository'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.odi.core.datasource.provider.JndiDataSourceProvider.doCreateDataSource(JndiDataSourceProvider.java:46)
... 100 more

后来发现weblogic的数据源中，有两个JNDI的名称是一致的，因此导致了在部署时的报错，修改其中的JNDI名称后能正常启动。