Adop Cutover Failed by "[UNEXPECTED]Error occurred starting Admin Server" on Run File System

(Doc ID 2314018.1)

Last updated on OCTOBER 06, 2017

Applies to:

Oracle Applications DBA - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

You can see the following error in an adop log file.

  [UNEXPECTED]Error occurred running "sh /u01/app/dev01/fs2/inst/apps/xxx_yyyyy/admin/scripts/adadminsrvctl.sh start -nopromptmsg -silent forcepatchfs"
  [UNEXPECTED]Error running adadminsrvctl command
  [UNEXPECTED]Error occurred starting Admin Server
  [UNEXPECTED]Cutover phase has failed.


In addition, the following error stack exist in "$LOG_HOME/appl/admin/log/adadminsrvctl.txt" .

09/08/17-14:58:01 :: adadminsrvctl.sh: exiting with status 1

================================================================================

09/08/17-17:00:05 :: adadminsrvctl.sh version 120.10.12020000.10
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv
Checking if the Admin Server is already up.
The Admin Server is not already up.
FMW Version is 11.1.1.9
Checking if the Node Manager is already up..
Connecting to Node Manager ...
Successfully Connected to Node Manager.

The Node Manager is already up.

Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Server 'AdminServer' has already been started

ERROR: Unable to connect the AdminServer.

StackTrace:
java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:212)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:97)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
at oracle.apps.ad.util.WLUtil.initMBeanServerConnection(WLUtil.java:131)
at oracle.apps.ad.tools.configuration.EBSProvisioner.ebs_nmstart_adminsrv(EBSProvisioner.java:3680)
at oracle.apps.ad.tools.configuration.EBSProvisioner.ebs_nmstart_adminsrv(EBSProvisioner.java:3866)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at oracle.apps.ad.tools.configuration.EBSProvisioner.main(EBSProvisioner.java:8834)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: ://yyyyy.zzzz.com:7000: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792)
:
:

 

Changes

 

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