My Oracle Support Banner

BIP.Delivery.WCC.Q' didn't find subcontext 'WCC During Startup After BIP Upgrade From 11.1.1.5 To 11.1.1.9 And Weblogic Upgrade 10.3.6.0 (Doc ID 2033348.1)

Last updated on FEBRUARY 03, 2019

Applies to:

BI Publisher (formerly XML Publisher) - Version 11.1.1.9.0 to 11.1.1.9.0 [Release 11.1]
Information in this document applies to any platform.

Symptoms

Recently upgraded Weblogic server from 10.3.5.0 to 10.3.6.0 and BIP from 11.1.1.5 to 11.1.1.9 and while starting the weblogic servers, we see errors/warnings in the startup log:

ConfigCheckServlet.init failed to start Scheduler.::
While trying to lookup 'BIP.Delivery.WCC.Q' didn't find subcontext 'WCC'. Resolved 'BIP.Delivery'::
javax.naming.NameNotFoundException: While trying to lookup 'BIP.Delivery.WCC.Q' didn't find subcontext 'WCC'. Resolved 'BIP.Delivery'; remaining name 'WCC/Q'
  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)

Changes

 Upgrade from an earlier version of BIP 11g to BIP 11.1.1.9.

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
References


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