My Oracle Support Banner

Running "adProvisionEBS.pl" to Integrate OAM 11gR2 With EBS 12.2, Error Occurs With Code "jdbc.OAEADatasourceDS" "newNameNotFoundException" (Doc ID 1947202.1)

Last updated on JANUARY 04, 2022

Applies to:

Oracle E-Business Suite Technology Stack - Version 12.2 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.

Symptoms

On Oracle Applications  12.2.4 version,
when attempting to run perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-oaea_resources,
the following error occurs:

Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.OAEADatasourceDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/OAEADatasourceDS'
    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)



The issue can be reproduced at will with the following steps:
1. Run the script.
2. Error occurs.

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.