My Oracle Support Banner

Starting the NMS Managed Server Fails and Results in "Org.omg.CORBA.COMM_FAILURE: Cound Not Get Naming Context" Error (Doc ID 2272357.1)

Last updated on SEPTEMBER 13, 2022

Applies to:

Oracle Utilities Network Management System - Version and later
Oracle Network Management for Utilities - DMS - Version and later
Information in this document applies to any platform.


Attempting to restart the NMS managed server fails.

Following the steps in <Document 1533273.1> did not start the managed server.

Using the Force Shutdown command did not stop the managed server.

Using "kill -9", they were able to stop the node manager and the NMS managed server.
They deleted the deployment and stopped the Admin server.

They then restarted all NMS services, the node manager and the Admin server, and then the empty NMS managed server.

As soon as they deployed the cesejb.ear file to the managed server, they would get the same error in the log file:

ERROR com.splwg.oms.ejb.session.Agent: org.omg.CORBA.COMM_FAILURE: Cound not get naming context vmcid: 0x0 minor code: 0 completed: No

If they deleted the JDBC connections and then recreated them, the first start up would work fine.  However all subsequent restarts would fail with the same error.


There was an unrelated database patch installed.


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.