My Oracle Support Banner

Unable To Start Managed Server In OAM Domain (Doc ID 2080515.1)

Last updated on NOVEMBER 05, 2019

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


After attempting to start the OAM managed server against the incorrect AdminServer, the OAM managed server startup fails.  For example, the OAM Domain's AdminServer listens on port <PORT1>.  Another domain's AdminServer (in this case, OIF) listens on port <PORT2>.  After attempting to start OAM managed with the command:


We see the following error:

There are 1 nested errors: [Management:141223]The server name <OAM_SERVER> specified with -Dweblogic.Name does not exist. The configuration includes the following servers {<ADMIN_SERVER>,<OIF_SERVER>}.
  at weblogic.t3.srvr.ServerServicesManager.startService(
  at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(
  at weblogic.t3.srvr.T3Srvr.initializeStandby(
  at weblogic.t3.srvr.T3Srvr.startup(
  at weblogic.Server.main(

Subsequent attempts to start the OAM managed server using the correct port still fail with the same error.




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.