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

Last updated on JUNE 06, 2017

Applies to:

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

Symptoms

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 7001.  Another domain's AdminServer (in this case, OIF) listens on port 7002.  After attempting to start OAM managed with the command:

$DOMAIN_HOME/bin/startManagedWebLogic.sh oam_server1 http://myhost.oracle.com:7002

We see the following error:

 

There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name oam_server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer,wls_oif1}.
  at weblogic.management.provider.internal.RuntimeAccessImpl.(RuntimeAccessImpl.java:149)
  at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
  at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
  at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
  at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
  at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
  at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
  at weblogic.Server.main(Server.java:71)

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

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms