12c Cloud Control: Understanding OMS Process Control (Start / Stop / To

Status) (Doc ID 1432335.1) Bottom

In this Document

Purpose
Scope
Details
Pre-requisites
Starting, Stopping, and Checking the Status of the 12c OMS
List of Operating System Processes Started by 12c OMS
Enabling or disabling the automatic startup of the OMS at the Server start
Log / Trace files Generated during the 12c OMS Startup
References

APPLIES TO:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later

Information in this document applies to any platform.

PURPOSE

This document provides details about the commands that can be used for controlling (start /
stop / status) the 12c OMS and the OS level processes which get started.

For details of the directory structure and useful locations in the 12c OMS home, refer to
Note 1368503.1 : 12c Cloud Control: Details of the Directory Structure and Commonly Used
Locations in a 12c OMS Installation.

SCOPE

12c Cloud Control Administrators who need to understand the steps involved in the OMS
process control.

DETAILS

Pre-requisites

The 12c Enterprise Manager Cloud Control setup consists of these components:

- Oracle Management Services (OMS)

- Oracle Management (Cloud Control) Repository, hosted in a certified Oracle Database.
- Oracle Management (Cloud) Agent, installed on the target machines (including the OMS
machine as well), which need to be monitored from Grid Console.

Before starting the 12c OMS:

The Repository Database and the Listener servicing this database should be up and
running.

These user accounts: sysman, sysman_opss, sysman_mds in the Repository database

should be open:

select username, account_status from dba_users where username in

('SYSMAN','SYSMAN_MDS','SYSMAN_OPSS');

USERNAME ACCOUNT_STATUS
--------------- ---------------
SYSMAN OPEN
SYSMAN_OPSS OPEN
SYSMAN_MDS OPEN

The passwords for the sysman, sysman_opss, sysman_mds should not have been
manually modified in the Repository database. Any password change should be
performed via the emctl utility using the steps in Note 1365930.1: 12c Cloud Control:
How to Modify the Password for SYSMAN and other Enterprise Manager Users at the
OMS Level and Repository Database?

If the Repository Database is running on a remote machine:

o From the OMS machine, the hostname lookup must succeed and IP address of the
database machine must be reachable.

o The two-way communication between OMS machine to Database Listener port

should be open (ie. not blocked by any kind of firewall).

The OMS should be started by the same OS user who has installed the Cloud Control
software in the machine.

Starting, Stopping, and Checking the Status of the 12c OMS

The OMS must be started using the Enterprise Manager Control utility - emctl located
in <OMS_HOME>/bin. emctl 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 OMS installation>

export PATH=$ORACLE_HOME/bin:$PATH

Or navigate to the <OMS_HOME>/bin directory and execute emctl:

cd <OMS_HOME>/bin
./emctl start|stop|status oms

Command Options

Usage and Typical Output Description

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
- Starts the opmn 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
- Starts the Managed server (EMGC_OMSn) through the Nod
Note:
- The components started by this command depend on the com
components: 'emctl stop oms' OR
'emctl stop oms -all'.

- emctl utility is capable of recognizing which components ha

- Value of the below parameter in the <EM_INSTANCE_BAS

used to determine whether the Admin Server is on the local m

IS_ADMIN_HOST=true

- The 12c EM Managed Server has two applications:

successfully for the OMS startup to be successful and to be sh
emctl status oms Checks the status of the Webtier (http_server, opmn) and the O
Oracle Enterprise Manager Cloud Control 12c OMS is shown as up only if both the emgc and
Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation.
All rights reserved.
WebTier is Up
Oracle Management Server is Up
emctl status oms -details This command is very useful in checking details of the ports a
Oracle Enterprise Manager Cloud Control 12c console access:
Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. - Prompts for the SYSMAN password.
All rights reserved. - Provides details of the HTTP (s) Console ports and the Agen
Enter Enterprise Manager Root (SYSMAN) - Reports whether OMS is configured to an SLB / Virtual host
Password : - Reports whether the Agent Upload and Console Access are l
Console Server Host : omsmachine.domain - Reports the number of active Certificate Authorities in the R
HTTP Console Port : 7789 - Displays the actual Console and Upload URL's for the Cloud
HTTPS Console Port : 7801 - Provides the WLS Domain name and Admin Server machine
HTTP Upload Port : 4890 - Provides details about the EM Managed Server.
HTTPS Upload Port : 4901
OMS is not configured with SLB or virtual Note: This command can be executed even if the OMS is dow
hostname
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
emctl stop oms - Stops the Webtier (http_server, opmn)
Oracle Enterprise Manager Cloud Control 12c - Stops the EM Managed server.
Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. Note: This command does not stop the Node Manager and the
All rights reserved.
Stopping WebTier...
WebTier Successfully Stopped
Stopping Oracle Management Server...
Oracle Management Server Successfully
Stopped
Oracle Management Server is Down
emctl stop oms -all - Stops the Webtier (http_server, opmn)
Oracle Enterprise Manager Cloud Control 12c - Stops the EM Managed server.
Release 12.1.0.1.0 - Stops the Admin server, if the OMS is running on Admin Ser
Copyright (c) 1996, 2011 Oracle Corporation. - Stops the Node Manager.
All rights reserved. - Also stops the ADP Manager, JVMD Manager and BIP proce
Stopping WebTier...
WebTier Successfully Stopped
Stopping Oracle Management Server...
Oracle Management Server Successfully
Stopped
AdminServer Successfully Stopped
Oracle Management Server is Down
emctl stop oms -force - Kills all the processes forcefully, should be used only when t
Oracle Enterprise Manager Cloud Control 12c - Can be used with/without -all option
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
emctl list oms - Provides the EM Managed Server name configured in that lo
Oracle Enterprise Manager Cloud Control 12c - If the Admin server is configured on the same host, it display
Release 12.1.0.1.0 EMGC_OMS1*.
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 Cloud Console like the ADP Manager,
JVMD Manager, BIP need to be started manually using the WLS Admin Console.

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 f
ile.

6. The 12c 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. 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

List of Operating System Processes Started by 12c OMS

There are two main processes: opmn and Java (NodeManager) both with a ppid of 1. These start
other processes as listed below:

1. opmn
 ||
opmn
||
|| ---> httpd.worker (for HTTP server)

The opmn process spawns another opmn process which is responsible for starting and
monitoring the HTTP server. Can be viewed on Unix using:

$ ps -aef | grep -i opmn

One process for HTTP_Server:

<MW_HOME>/Oracle_WT/ohs/bin/httpd.worker -DSSL

This in turn spawns many other 'httpd.worker

-DSSL', rotatelogs, odl_rotatelogs processes as needed. Can be viewed on Unix using:

$ ps -aef | grep -i ohs

2. Java (Nodemanager)
||
||
||---> startEMServer.sh
|| ||
|| || ---> startWebLogic.sh
|| ||
|| || ---> EMGC_ADMINSERVER
||
||---> startEMServer.sh
||
|| ---> startWebLogic.sh
||
|| ---> EMGC_OMSn

The NodeManager java process is responsible for starting and monitoring the Admin
Server and the EM Managed Server.
Can be viewed on Unix using:

$ ps -aef | grep -i NodeManager

This further spawns two shells, each running the startEMServer.sh script.

Both the shells further invoke startWebLogic.sh script.

One of the shell running startWebLogic.sh script starts the EMGC_ADMINSERVER.

 This is present only on the primary OMS machine. Can be viewed on Unix using:

$ ps -aef | grep EMGC_ADMINSERVER

The other shell running the startWebLogic.sh script starts the EM Managed Server. Can
be viewed on Unix using:

$ ps -aef | grep EMGC_OMS

You can also view the entire list of processes using other OS tools like:

$ pstree -capG <OS user>

where <OS user> is the Operating system user who has installed and started the OMS.

Enabling or disabling the automatic startup of the OMS at the Server start

This is fully documented in:

Enterprise Manager Cloud Control Advanced Installation and Configuration Guide

2 Understanding the Basics
2.7 Understanding the Startup Scripts

Log / Trace files Generated during the 12c OMS Startup

The following log/trace files are updated during the OMS startup:
These files should be checked when the oms fails to start or when any Cloud Control component
fails to start.

Component Files Location

emctl emctl.log <EM_INSTANCE_BASE>/em/EMGC_OMSn/sysma
OPMN opmn.log <EM_INSTANCE_BASE>/WebTierIH1/diagnostics/

HTTP_SERVER access_log, <EM_INSTANCE_BASE>/WebTierIH1/diagnostics/

console~OHS~1.log

EM Node Manager nodemanager.log <EM_INSTANCE_BASE>/NodeManager/emnodema

(only, if the node
manager is started)
Admin Server EMGC_ADMINSERVER.out, <EM_INSTANCE_BASE>/user_projects/domains/G
(only on the primary EMGC_ADMINSERVER.log,
OMS machine and if the GCDomain.log
Admin Server is started)
EM Managed Server EMGC_OMS1.out, <EM_INSTANCE_BASE>/user_projects/domains/G
EMGC_OMS1.log

To troubleshoot the OMS startup / shutdown failure, emctl.log file is the starting point to look at.

Based on each component that is being started, you can then look at the Webtier, Nodemanager,
Admin server and EM Managed server logs.