My Oracle Support Banner

Intermittent Error After Processing Capture Batches "javax.naming.NameNotFoundException: Unable to resolve 'jdbc.Barcode_DBLookup'. Resolved 'jdbc'; remaining name 'Barcode_DBLookup'" (Doc ID 2919952.1)

Last updated on JANUARY 10, 2023

Applies to:

Oracle WebCenter Enterprise Capture - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

After an upgraded to Capture 12.2.1.4.0, an issue occurs where 4 or 5 batches per day (out of 400 batches a day) do not get committed. They end up in the Capture client with an error:

javax.naming.NameNotFoundException: Unable to resolve 'jdbc.Barcode_DBLookup'. Resolved 'jdbc'; remaining name 'Barcode_DBLookup'

The stack trace in the Capture managed server diagnostic log file shows as:

[2022-11-21T03:07:59.292-05:00] [capture_server1] [ERROR] [] [oracle.dc.admin.view.workspace.WorkspacesManager] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <USERID>] [ecid: <ECID>] [APP: capture] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: <DSID>] Error opening database connection[[
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.CaptureDBLookup'. Resolved 'jdbc'; remaining name 'CaptureDBLookup'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:354)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:227)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:532)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:228)
at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:532)
at weblogic.jndi.internal.RootNamingNode.lookup(RootNamingNode.java:84)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:307)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:435)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at oracle.odc.util.DBUtil.getJDBCConnection(DBUtil.java:38)
at oracle.dc.admin.view.dblookup.LookupManager.connectDB(LookupManager.java:284)
at oracle.dc.admin.view.dblookup.LookupManager.initializer(LookupManager.java:116)

Releasing the problematic batch from the Capture client again goes through without any errors.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution


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