My Technical Works: April 2013

Oracle Enterprise Manager 12c : Managing Components

This summary is not available. Please click here to view the post.

Oracle Enterprise Manager 12C : More Details

OMS Start Up

When you start the Management Service, the following services are started:

OPMN process. This is the watchdog for the Apache process. The OPMN process starts the Apache process if it crashes.

Apache processes to start the HTTP server

Node Manager Java process. This is the watchdog for the Managed Server and Admin Server processes. It restarts the Managed Server and Admin Server processes if they crash.

Admin Server Java process (if the command to start OMS is executed on the first OMS machine). This is the WebLogic Server instance that maintains configuration data for configured Enterprise Manager domain.

Managed Server Java process. This is the Managed WebLogic Server on which Enterprise Manager application is deployed.

Logging Details

emctl log file

$INSTANCE_HOME/em/EMGC_OMS<n>/sysman/log/

Managed Server log files

$INSTANCE_HOME/user_projects/domains/<DOMAIN_NAME>/servers/EMGC_OMS<n>/logs/EMGC_OMS<n>.log

$INSTANCE_HOME/user_projects/domains<DOMAIN_NAME>/servers/EMGC_OMS<n>/logs/EMGC_OMS<n>.out

OMS log files

$INSTANCE_HOME/em/EMGC_OMS<n>/sysman/log/

$INSTANCE_HOME/em/EMGC_OMS<n>/sysman/log/emoms_pbs.trc

$INSTANCE_HOME/em/EMGC_OMS<n>/sysman/log/emoms.trc

$INSTANCE_HOME/em/EMGC_OMS<n>/sysman/log/emoms.log

(In an environment with multiple OMS instances, <n> refers to the number of the OMS in the environment.)

Node Manager log files

$INSTANCE_HOME/NodeManager/emnodemanager/nodemanager.log

Admin Server log files

INSTANCE_HOME/WebTierIH1/diagnostics/logs/OHS/ohs1/access_log

WebTier Service Fails to Start

Check logs under <WebTier Instance Home>/diagnostics folder in case WebTier start fails.

To Verify Plugin Installation

Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed.

$<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log

Oracle Enterprise Manager 12C : Agent Installation

This summary is not available. Please click here to view the post.

Oracle Enterprise Manager 12C: Directory Structure

In The Thrid Series Of Oracle Enterprise Manager 12c, we see the Directory Structure

Oracle Management Service home directory

Middleware WebTier home directory

Middleware Common home directory

Oracle Management Service Instance home directory

Oracle Management Agent home directory

Oracle Management Service Plugins home

Oracle Management Agent Plugin home

The Oracle Management Service is a J2EE application that is installed and deployed using the Oracle WebLogic Server.

The Env Variable Configuration Based on the Installation That Did on my PC

ORACLE_HOME=/software/oem/oem

OMS_INSTANCE_HOME=/software/oem/oem/gc_inst

ORACLE_HOME/bin = The bin directory in the Management Service home contains commands used to control the components of the Cloud Control installation.

OMS_INSTANCE_HOME=This directory contains configuration files for OMS home. The default OMS_INSTANCE_HOME location is gc_inst.

OMS_INSTANCE_HOME/WebTierIH1=This directory contains WebTier instance Oracle Home corresponding to EMGC_OMS#.

OMS_INSTANCE_HOME/NodeManager = This directory contains WebLogic Node Manager properties, logs, and domain information.

OMS_INSTANCE_HOME/em = This is the OMS instance directory and contains emgc.properties and Enterprise Manager log files.

OMS_INSTANCE_HOME/user_projects = This directory contains EMGC_ADMINSERVER and EMGC_OMS# domains and their logs.

The Directory Structure for the Installation is as follows

domain-registry.xml

gc_inst

jdk16

logs

modules

ocm.rsp

oms

oracle_common

Oracle_WT

patch_wls1035

plugins

registry.dat

registry.xml

user_projects

utils

wlserver_10.3

Directory gc_inst is ORACLE_INSTANCE that contains OHS instance (gc_inst/WebTierIH1) and Weblogic Domain (gc_inst/user_projects)

WebLogic Server will create Domain with 1 Admin Server and 1 Managed Server as shown below WebLogic Admin Server (EMGC_ADMINSERVER) & Managed Server (EMGC_OMS1)

wlserver_10.3, logs, utils, modules : These directories contain Fusion Middleware files.

jdk16 : This directory contains JDK configuration files.

oms : This directory contains OMS configuration files. For more information, see Section 10.2.2.

plugins : This directory contains metadata plug-ins configuration files installed on the OMS.

oracle_WT : This directory contains Oracle WebTier configuration files.

oracle_common : This directory contains common files used by OMS, Oracle WebTier, and WebLogic Server directories.

Oracle Management Agent

The Oracle Management Agent is installed automatically when you install Oracle Management Service. This local instance of the Oracle Management Agent gathers management information about the targets on the Oracle Management Service host. You can then manage those targets, such as the host itself, from the Cloud Control Console.

agentimage.properties

agent_inst

core

plugins

sbin

AGENT_BASE_DIR=/software/oem/oms

Four Dir Structure are configured

AGENT_HOME=/software/oem/oms/core/12.1.0.2.0/

AGENT_INSTANCE_HOME=/software/oem/oms/agent_inst

AGENT_INSTANCE_HOME/bin= The AGENT_INSTANCE_HOME/bin directory in the Cloud Control Home contains the emctl command that controls the Oracle Management Agent for this host.

You use the following emctl commands in this directory to start and stop the Oracle Management Agent on this host:

<AGENT_INSTANCE_HOME>/bin/emctl start agent

<AGENT_INSTANCE_HOME>/bin/emctl stop agent

SBIN_HOME=/software/oem/oms/sbin

PLUGIN_HOME=/software/oem/oms/plugins

Oracle Enterprise Manager 12C : Installation of OEM 12C

In The Second Phase we see how to Install the OEM 12C

Installation Requirements

Let’s see the Requirements on the Hardware Side. There are 3 components to be installed

Oracle Management Service (OMS)

Oracle Management Agents (Management Agents)

Oracle Management Repository (Management Repository), since the Repository is already available we don’t deal with this.

Management Service

Hardware	<1000 Targets 1 OMS <100 Agents <10 Current Sessions	>=1000 & <10,000 Targets 2 OMS >=100 but <1000 Agents >=10 but <25 Concurrent User Sessions	>=10,000 Targets > 2 OMS >=1000 Agents >=25 but <=50 Concurrent User Sessions
CPU Core	2	4	8
RAM	6GB	8GB	16GB
File System	7GB	7GB	7GB

Management Agent

Stand alone Agent: 2 CPU Cores Per Host, 512MB Ram,1 GB File System.

Master Agent: 2 CPU Cores Per Host, 512MB Ram, 1 GB File System.

[root@someThing install]$ uname -a

Linux omhq188e 2.6.32-279.19.1.el6.x86_64 #1 SMP Sat Nov 24 14:35:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

Package, kernel and Library Requirements

1 .Oracle Management Service

Requires Packages (Specific to Red hat 6.x)

make-3.81
binutils-2.17.50.0.6
gcc-4.1.1
libaio-0.3.106
glibc-common-2.3.4
libstdc++-4.1.1
sysstat-5.0.5
glibc-devel-2.5-49-i686 (This is a 32-bit package)
glibc-devel-2.5-49-x86_64 (This is a 64-bit package)

Check For the packages

[root@someThing install]$ yum list installed | grep make

make.x86_64 1:3.81-20.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep binutils

binutils.x86_64 2.20.51.0.2-5.34.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep gcc

gcc.x86_64 4.4.6-4.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

libgcc.i686 4.4.6-4.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

libgcc.x86_64 4.4.6-4.el6 @anaconda-RedHatEnterpriseLinux-

201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep libaio

libaio.x86_64 0.3.107-10.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

libaio-devel.x86_64 0.3.107-10.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep libstdc

libstdc++.i686 4.4.6-4.el6 @dev-rhel-x86_64-server-6

libstdc++.x86_64 4.4.6-4.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep sysstat

sysstat.x86_64 9.0.4-20.el6 @anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3

[root@someThing install]$ yum list installed | grep glibc-devel

glibc-devel.x86_64 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

2. Oracle Management Agent

Requires Packages (Specific to Red hat 6.x)

make-3.81
binutils-2.17.50.0.6
gcc-4.1.1
libaio-0.3.106
glibc-common-2.3.4
libstdc++-4.1.1
sysstat-5.0.5

Kernel Requirements

kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295

kernel.shmmax : Controls the maximum shared segment size, in bytes

[root@someThing install]$ cat /proc/sys/kernel/shmmax

68719476736

Library Requirements

1. Oracle Management Service

glibc-2.5-12 for Both 32bit and 64bit

Glibc features high performance and a high degree of portability (i.e., is easy to port) to both new processors and kernels. Moreover, it complies with all relevant industry standards and is also internationalized

[root@someThing install]$ yum list installed | grep glibc

glibc.i686 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

glibc.x86_64 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

glibc-common.x86_64 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

glibc-devel.x86_64 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

glibc-headers.x86_64 2.12-1.80.el6_3.6 @dev-rhel-x86_64-server-6

2. Oracle Management Service

NONE

Software needed:

1. OS: RHEL/OEL 4, 5 or 6 with packages, kernel settings and users mentioned in install doc.

2. Oracle database 11.2.0.3 with parameters, tablespaces and users mentioned in install doc.

3. JDK and Weblogic server comes with 12c software (for 11g EM we need to install them separately).

Hardware:

RAM

[root@someThing install]$ cat /proc/meminfo

MemTotal: 32844872 kB

MemFree: 24189776 kB

We have 32GB available.

Processors

No Of Processors

[root@someThing install]$ cat /proc/cpuinfo | grep physical.id | sort -u | wc -l

No Of CPU Cores

[root@someThing install]$ grep cpu.cores /proc/cpuinfo | sort -u

cpu cores : 4

Hard disk

50GB for OMS + 15 GB for OS = 85GB

[root@someThing install]$ cat /proc/partitions

major minor #blocks name

8 0 439514302 sda

8 1 524288 sda1

8 2 438988800 sda2

253 0 2097152 dm-0

253 1 4194304 dm-1

253 2 1048576 dm-2

253 3 1048576 dm-3

253 4 52428800 dm-4

253 5 524288 dm-5

253 6 1048576 dm-6

253 7 4194304 dm-7

253 8 4194304 dm-8

253 9 131072 dm-9

253 10 131072 dm-10

253 11 4194304 dm-11

253 12 4194304 dm-12

Check The File Descriptors

[root@someThing install]$ ulimit -a

core file size (blocks, -c) 0

data seg size (kbytes, -d) unlimited

scheduling priority (-e) 0

file size (blocks, -f) unlimited

pending signals (-i) 256451

max locked memory (kbytes, -l) 64

max memory size (kbytes, -m) unlimited

open files (-n) 4096

pipe size (512 bytes, -p) 8

POSIX message queues (bytes, -q) 819200

real-time priority (-r) 0

stack size (kbytes, -s) 10240

cpu time (seconds, -t) unlimited

max user processes (-u) 1024

virtual memory (kbytes, -v) unlimited

file locks (-x) unlimited

Make sure that SELINUX and firewall are disabled

Find the Run level

[root@someThing install]$ runlevel

N 3

Check Whether Iptables is Disabled

[root@someThing install]$ chkconfig --list | grep iptables

iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off

Check Whether Selinux is Disabled

[root@someThing install]$ cat /etc/selinux/config

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:

# enforcing - SELinux security policy is enforced.

# permissive - SELinux prints warnings instead of enforcing.

# disabled - SELinux is fully disabled.

SELINUX=disabled

# SELINUXTYPE= type of policy in use. Possible values are:

# targeted - Only targeted network daemons are protected.

# strict - Full SELinux protection.

SELINUXTYPE=targeted

Make sure that you use unique host names and static IP addresses. Do not use Virtual IP or Virtual hostnames or SCANs.

Make sure that a physical host name is used and is fully resolvable. Make sure that all nslookup queries resolve to the same name and associated IP address.

[root@someThing install]$ nslookup omhq188e

Server: 167.132.254.225

Address: 167.132.254.225#53

omhq188e.uprr.com canonical name = eth0.omhq188e.uprr.com.

Name: eth0.omhq188e.uprr.com

Address: 69.58.250.37

Installing the Oracle Enterprise Manager

1.Enter the Details for the Oracle Support ( If available )