Connecting To Data Source Error After Configuring Endeca Fails With Element ERROR_AUDIT_UPDATE:Error Audit Update-Component pre-execute initialization failed (Doc ID 2052838.1)

Last updated on OCTOBER 20, 2016

Applies to:

Oracle EBS Extensions for Oracle Endeca - INSTALL - Version 12.1.3.1 to 12.1.3.1 [Release 12.1]
Information in this document applies to any platform.

Symptoms

On Oracle Applications Endeca 12.1.3.1 version,
when attempting to run a Full Graph, it fails and an error appear in the child log:

Element ERROR_AUDIT_UPDATE:Error Audit Update-Component pre-execute initialization failed.
at org.jetel.graph.Node.run(Node.java:446)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.jetel.exception.JetelException: Cannot establish DB connection to JNDI:jdbc/ebsdb While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved '' caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'
at org.jetel.component.DBExecute.initConnection(DBExecute.java:481)
at org.jetel.component.DBExecute.preExecute(DBExecute.java:415)
at org.jetel.graph.Node.run(Node.java:444)
... 3 more
Caused by: org.jetel.exception.JetelException: Cannot establish DB connection to JNDI:jdbc/ebsdb While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved '' caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'
at org.jetel.connection.jdbc.DBConnection.connect(DBConnection.java:484)
at org.jetel.connection.jdbc.DBConnection.getConnection(DBConnection.java:465)
at org.jetel.component.DBExecute.initConnection(DBExecute.java:478)
... 5 more
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.ebsdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/ebsdb'
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:412)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at org.jetel.connection.jdbc.DBConnection.connect(DBConnection.java:477)
... 7 more
2015-08-18 16:50:42,596 ERROR 196127 WatchDog  Phase finished with error - stopping graph run

 

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