My Oracle Support Banner

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

Last updated on FEBRUARY 20, 2019

Applies to:

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


Recently upgraded Weblogic server from to and BIP from to 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(
  at weblogic.jndi.internal.BasicNamingNode.lookupHere(
  at weblogic.jndi.internal.ServerNamingNode.lookupHere(
  at weblogic.jndi.internal.BasicNamingNode.lookup(


 Upgrade from an earlier version of BIP 11g to BIP


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

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