The OMS must be started using the Enterprise Manager Control utility – emctl located in [OMS_HOME]/bin. If the actual OMS_HOME is not known, there should be an entry in the /etc/oragchomelist file (for HPia64 and Solaris SPARC, the file is /var/opt/oracle/oragchomelist) for the OMS Home. The emctl script is a command-line utility to start, stop, or check the status of the EM components. It is a shell script which sets all the right environment (to launch perl, java, etc.) for starting the OMS and then invokes the emctl.pl script with appropriate arguments (start / stop / status).
Set these environment variables:
$ export ORACLE_HOME=[path of the 12c/13c OMS installation] export PATH=$ORACLE_HOME/bin:$PATH
Or navigate to the [OMS_HOME]/bin directory and execute emctl:
$ cd/bin $ ./emctl start|stop|status oms
Command Options
All the examples shown below are from an EM 12c OMS. But the same commands applies for the 13c and above versions as well.
Start EM Cloud Control OMS
– Starts the opmn (12c only) and HTTP_SERVER (OHS), if not already up.
– Starts the Node Manager, if not running.
– Checks if the Admin Server is configured on the machine. If yes, starts the Admin Server, if already not up.
– Starts the Managed server (EMGC_OMSn) through the Node Manager.
emctl start oms Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. Starting WebTier... WebTier Successfully Started Starting Oracle Management Server... Oracle Management Server Successfully Started Oracle Management Server is Up
Note:
– The components started by this command depend on the command which was earlier used to stop the OMS components: ’emctl stop oms’ OR ’emctl stop oms -all’.
– emctl utility is capable of recognizing which components have to be started and no user intervention required.
– Value of the below parameter in the [EM_INSTANCE_BASE]/em/EMGC_OMS1/emgc.properties file is used to determine whether the Admin Server is on the local machine or not.
IS_ADMIN_HOST=true
– The EM Cloud Control Managed Server has two applications: emgc and empbs. Both of these should start up successfully for the OMS startup to be successful and to be shown as Up in the command output.
Check status of EM Cloud Control OMS
– Checks the status of the Webtier (http_server, opmn) and the OMS and provides the current status.
– OMS is shown as up only if both the emgc and empbs applications are accessible.
emctl status oms Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. WebTier is Up Oracle Management Server is Up
Check status of EM Cloud Control OMS (detailed version)
This command is very useful in checking details of the ports and secure access for the Agent upload and console access:
– Prompts for the SYSMAN password.
– Provides details of the HTTP (s) Console ports and the Agent Upload Ports.
– Reports whether OMS is configured to an SLB / Virtual host name or not.
– Reports whether the Agent Upload and Console Access are locked in secure mode or not.
– Reports the number of active Certificate Authorities in the Repository.
– Displays the actual Console and Upload URL’s for the Cloud Control setup.
– Provides the WLS Domain name and Admin Server machine name
– Provides details about the EM Managed Server.
emctl status oms -details Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : Console Server Host : omsmachine.domain HTTP Console Port : 7789 HTTPS Console Port : 7801 HTTP Upload Port : 4890 HTTPS Upload Port : 4901 OMS is not configured with SLB or virtual host name Agent Upload is locked. OMS Console is locked. Active CA ID: 1 Console URL: https://omsmachine.domain:7801/em Upload URL: https://omsmachine.domain:4901/empbs/upload WLS Domain Information Domain Name : GCDomain Admin Server Host: omsmachine.domain Managed Server Information Managed Server Instance Name: EMGC_OMS1 Managed Server Instance Host: omsmachine.domain
Stop EM Cloud Control OMS
– Stops the Webtier (http_server, opmn)
– Stops the EM Managed server.
emctl stop oms Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped Oracle Management Server is Down
Stop all components
– Stops the Webtier (http_server, opmn)
– Stops the EM Managed server.
– Stops the Admin server, if the OMS is running on Admin Server host.
– Stops the Node Manager.
– Also stops the ADP Manager, JVMD Manager and BIP processes, if running.
emctl stop oms -all Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped AdminServer Successfully Stopped Oracle Management Server is Down
Stop forcefully
– Kills all the processes forcefully, should be used only when the normal stop does not work.
– Can be used with/without -all option.
emctl stop oms -force Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped Oracle Management Server is Down
Check EM Managed Server name
– Provides the EM Managed Server name configured in that local ORACLE home.
– If the Admin server is configured on the same host, it displays a ‘*’ next to OMS name e.g. EMGC_OMS1*.
emctl list oms Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved. OMS Instance(s) associated with current Oracle Home: EMGC_OMS1*
Note
1. emctl can control / manage local processes on that machine only, there is no option to start / stop an OMS on a remote machine.
2. Any additional products that are installed with 12c/13c Cloud Console like the ADP Manager, JVMD Manager, BIP need to be started manually using the WLS Admin Console. Starting with 13c, these are started automatically when the “emctl start oms” command is executed.
3. There is no need to modify or execute any Weblogic scripts such as startManagedWebLogic.sh and startWebLogic.sh for starting up the components as all the necessary components are started by the ’emctl start oms’ itself.
4. It is also not necessary to set any WLS related environment variables.
5. If any environment or Java related parameters need to be set for the OMS, they can be added to the [EM_INSTANCE_BASE]/user_projects/domains/GCDomain/servers/bin/startEMServer.sh file.
6. The Cloud Control OMS installation configures a new EM specific nodemanager at [EM_INSTANCE_BASE]/em/NodeManager/emnodemanager. Hence, the default nodemanager at the [MW_HOME]/wlserver_10.3/common/nodemanager should not be configured / started.
7. The [EM_INSTANCE_BASE]/em/NodeManager/emnodemanager/nodemanager.properties has the following set:
StartScriptName=startEMServer.sh StartScriptEnabled=true
These properties should not be modified.
8. (12c specific)The emctl script controls the Webtier (opmn and http_server) components by using the opmnctl utility.
– It starts the Webtier using:
[EM_INSTANCE_BASE]/WebTierIH1/bin/opmnctl startall
This command can be executed independently at the command line if only the Webtier needs to be started.
– To stop only the Webtier:
[EM_INSTANCE_BASE]/WebTierIH1/bin/opmnctl stopall
– To check the Webtier status:
[EM_INSTANCE_BASE]/WebTierIH1/bin/opmnctl status Processes in Instance: instance1 ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- ohs1 | OHS | 28197 | Alive