Unable To Resolve 'Oracledmsnotifier' Error Starting the Admin Server (Doc ID 956116.1)

Last updated on AUGUST 10, 2020

Applies to:

Oracle Fusion Middleware - Version 11.1.1.0.0 to 11.1.1.0.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms

This issue affects any Oracle Fusion Middleware (FMW) 11 installation type using Oracle Weblogic Server 10.3.1
A FMW domain has been successfully created, but when an attempt is made to start the Admin Server for the domain using :

$MIDDLEWARE_HOME/user_projects/domains/<domain_name>/bin/startWeblogic.sh

the following error is displayed to the console output:

<BEA-000000> <Failed to register registerMBean.
javax.naming.NameNotFoundException: Unable to resolve 'oracleDmsNotifier'. Resolved '';
remaining name 'oracleDmsNotifier'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
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)
:

There is no operational impact of this message, since the Admin Server proceeds to start successfully.

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

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

Unable To Resolve 'Oracledmsnotifier' Error Starting the Admin Server (Doc ID 956116.1)

Applies to:

Symptoms

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!