In this post I will be covering the installation & configuration of Oracle Enterprise Manager 13c

Release 1.

Oracle Enterprise Manager is a central management & monitoring solution for all Oracle products.
OEM is capable of monitoring many third party products as well and capable of sending alerts &
notifications based on the rules set by the administrators.

My Environment & Software Used

 Oracle Linux 6.7 64 Bit Virtual Machine
 VMware Workstation Player 12
 Oracle Database 12.1.0.2
 Oracle Enterprise Manager 13c Release 1 (13.1.0.0)

I have already built my Oracle Linux 6.7 64 Bit VMware with Oracle Database 12c pre-installed and
I will not be covering DB installation part here.

Package Requirements for Oracle Management Service (OMS)

 make-3.81
 binutils-2.20
 gcc-4.4.4
 libaio-0.3.107
 glibc-common-2.12-1
 libstdc++-4.4.4
 libXtst-1.0.99 (x86_64)
 sysstat-9.0.4
 glibc-2.12
 glibc-devel-2.12-1.7 (i686)
 glibc-devel-2.12-1.7 (x86_64)

Package Requirements for Management Agent

Below packages must be installed on the target machine where you are installing OEM Management
Agent.

 make-3.81
 binutils-2.20
 gcc-4.4.4
 libaio-0.3.107
 glibc-common-2.12-1.7
 libstdc++-4.4.4
 sysstat-9.0.4
Package Search & Installation
To check if the package is installed on the Oracle linux server, execute below command

1 rpm -qa | grep package_name

Sample output

1 [oracle@localhost ~]$ rpm -qa|grep make

2 make-3.81-20.el6.x86_64
To search for missing RPM using YUM, execute below command. If the server is not connected to
internet, download the RPM manually and install it.

1 yum search package_name

To install the RPM using YUM, execute below command

1 sudo yum install package_name

Kernel Requirements
 If OMS and Database are on different hosts, set kernel.shmmax parameter as below in
/etc/sysctl.conf

1 kernel.shmmax = 4294967295

 If OMS and Database are on same host, no special requirement for OMS and DB parameter
will take precedence.
 Add / change below line in /etc/sysctl.conf to set local port range to 11000 – 65000

net.ipv4.ip_local_port_range = 11000 65500

SQL> show parameter session_cached

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------
session_cached_cursors integer 50

SQL> alter system set session_cached_cursors=350 scope=spfile;

1
System altered.

SQL>
 SQL> show parameter shared_pool_size

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------
shared_pool_size big integer 0

SQL> alter system set shared_pool_size=1G scope=both;

System altered.

 Restart the server once above changes are made.

Users & Groups Requirement

 Create ‘oinstall’ group

1 groupadd oinstall

 Create ‘oracle’ user and add to ‘oinstall’ group

1 useradd oracle -g oinstall

 Login as ‘oracle’ user to perform the installation & configuration.

Database Requirement

Repository Database Creation Using Template

In this article, we are going to use the repository template to create the repository
database. If you are creating the database manually, remember to check all the
prerequisites here, some of which include the following.

 Database version 12.1.0.2 Enterprise Edition.

 You can use a Non-CDB database, or a PDB if you are not using the template to build
the repository. The database template provided by Oracle used in this article is still a
non-CDB database.
 The OPTIMIZER_ADAPTIVE_FEATURES initialization parameter should be set to FALSE.
  Character set AL32UTF8.

The template includes all the relevant database settings, but make sure the character
set is selected using the creation, as described below.

Unzip the repository template under the ORACLE_HOME.

$ cd $ORACLE_HOME/assistants/dbca/templates
$ unzip /tmp/12.1.0.2.0_Database_Template_for_EM13_1_0_0_0_Linux_x64.zip

Start the Database Configuration Assistant (DBCA) and create a new database using
the template.

$ dbca

Select the "Create Database" option and click the "Next" button.
Select the "Advanced Mode" option and click the "Next" button.
Select the template for the appropriate size of EM installation you need. In this case I've
used the small option. Click the "Next" button.
Enter the Global Database Name and SID, then click the "Next" button.
Make sure both the "Configure Enterprise Manager (EM) Database Express" and
"Register with Enterprise Manager (EM) Cloud Control" options are unchecked, then
click the "Next" button.
Enter the database credentials, then click the "Next" button.
Enter the listener details and click the the "Next" button.
Choose the preferred location for the database files, then click the "Next" button.
Accept the default settings and click on the "Next" button.
Amend the memory settings as desired, click on the "Character Sets" tab and select the
"AL32UTF8" option and click the "Next" button. In this case I'm accepting the memory
defaults.
Click the "Next" button to create the database.
If you are happy with the summary information, click the "Finish" button.
Wait while the database is created.
Once the database creation is complete, click the "Close" button.

 Set optimizer adaptive features to false

1 alter system set optimizer_adaptive_features=false scope=both sid='*';

 Check the value using show parameter

1 show parameter optimizer_adaptive_features

 Restart the Database

Core Components Installed
 Oracle Weblogic Server 12c Release 1 (12.1.3.0)
 JDK 1.7 – pre installed JDK is not supported from this release
 Oracle Management Service 13c Release 1
 Management Agent 13c Release 1
 Oracle JRF 12c Release 1 (12.1.3.0)
 Oracle Web Tier 12c Release 1 (12.1.3.0)
 Oracle BI Publisher 12c Release 1 (12.1.3.0)
 Default plug-ins Installed
o Oracle Database Plug-in
o Oracle Fusion Middleware Plug-in
o Oracle Exadata Plug-in
o Oracle Cloud Framework Plug-in
o Oracle System Infrastructure Plug-in

Things To Do Before Installation

 Unset ORACLE_HOME & ORACLE_SID if you have set them during your Database
installation on the same host
 Remove all Oracle directories from PATH. You can add them later after OEM installation
 Ensure Weblogic Server is dedicated to OMS as OMS cannot co-exist with any other Oracle
Fusion Middleware product
 Create config & cluster directories for BI Publisher

1 mkdir -p /u01/app/oracle/product/bip/config
2 mkdir -p /u01/app/oracle/product/bip/cluster
OEM Installation & Configuration
 OEM Cloud Control 13c Installation files
o em13100_linux64.bin (802 MB)
o em13100_linux64-2.zip (1.22 GB)
o em13100_linux64-3.zip (1.99 GB)
o em13100_linux64-4.zip (1.99 GB)
o em13100_linux64-5.zip (316 MB)
 It is not required to unzip the installation software. Provide execute permissions to oracle on
.bin file

1 chmod 755 em13100_linux64.bin

 Execute .bin file

1 ./em13100_linux64.bin
 Uncheck Security Updates & click Next

 Click Yes on the confirmation screen

 Select Skip and click Next on Software Updates Screen
 Make sure all the prerequisite checks are successful and click Next
o In my case I have warnings for kernel parameters and physical memory. I am
ignoring it as my port range is set to 11000 – 65500 & my physical memory is little
less than 10GB. Both values should be fine in my case.

 My local port range setting

 My physical memory setting

 Select Simple here and click Next

o In Advanced installation, you can customize ports, domain name, OMS instance
name & paths. Simple takes all default values. For demo purposes I have selected
Simple, but for production environments, select Advanced and customize as per your
needs
 Specify paths as below
o Middleware Home Directory : /u01/app/oracle/product/oemfmw_13c
o Agent Base Directory : /u01/app/oracle/product/agent_13c (make sure that your agent
base directory is outside your middleware home)
o Host Name : oraclelinux6.localdomain (provide FQDN here)
 Specify Administrator Password & Database Connection Details and click Next
o As it is Simple Installation, single password will be used for Weblogic,
Nodemanager, MDS, SYSMAN accounts. In Advanced installation, you will have an
option to select different password for each account.
o In the Database connection details, make sure you use SYS account and pluggable
database service name
 On this screen it will ask you to apply recommended parameters on the database. Click yes to
apply them automatically
 On this screen, you will see warning on session_cached_cursors & shared_pool_size. These
settings should be the values recommended. This is required in production environments as it
affects performance. You can do this after the OEM installation. I am leaving these settings
for my demo installation.
 Provide the paths for Software Library, BI Publisher config & cluster directories. These are
optional and can be configured from OEM console after the installation. But it is
recommended to configure during installation. You can also optionally enable BI Publisher
during installation or can be enabled using EMCTL after installation
o Software Library : /u01/app/oracle/product/swlib
o BI Publisher Config Directory : /u01/app/oracle/product/bip/config
o BI Publisher Cluster Directory : /u01/app/oracle/product/bip/cluster
 Review the details and click Install
 Installation Progress
 Configuration Progress
  The configuration process is a long running one. For me it took almost 3 hours. SO be

patient
 Once configuration is complete, execute below script as root

1 /u01/app/oracle/product/oemfmw_13c/allroot.sh

 Sample output

1 [root@oraclelinux6 ~]# /u01/app/oracle/product/oemfmw_13c/allroot.sh

2
3 Starting to execute allroot.sh .........
4
5 Starting to execute /u01/app/oracle/product/oemfmw_13c/root.sh ......
6 /etc exist
7
Creating /etc/oragchomelist file...
8 /u01/app/oracle/product/oemfmw_13c
9 Finished product-specific root actions.
10 /etc exist
11 Finished execution of /u01/app/oracle/product/oemfmw_13c/root.sh ......
Starting to execute /u01/app/oracle/product/agent_13c/agent_13.1.0.0.0/root.sh ......
12 Finished product-specific root actions.
13 /etc exist
14 Finished execution of /u01/app/oracle/product/agent_13c/agent_13.1.0.0.0/root.sh ....
15 [root@oraclelinux6 ~]#
16
17
  Click Close on Finish screen

 The installation & configuration process is complete now

Important Ports
 Enterprise Manager Upload HTTP Port : 4889
 Enterprise Manager Upload HTTP SSL Port : 4903
 OHS HTTP Port : 9788
 OHS HTTP SSL Port : 9851
 BI Publisher HTTP Port : 9701
 Enterprise Manager Central Console HTTP SSL Port : 7802
 Enterprise Manager Central Console HTTP Port : 7788
  Node Manager HTTP SSL Port : 7403
 BI Publisher HTTP SSL Port : 9803
 Managed Server HTTP Port : 7202
 Managed Server HTTP SSL Port : 7301
 Oracle Management Agent Port : 3872
 Admin Server HTTP SSL Port : 7102

Important URLs
 Enterprise Manager Cloud Control URL : https://oraclelinux6.localdomain:7802/em
 Admin Server URL : https://oraclelinux6.localdomain:7102/console
 BI Publisher URL : https://oraclelinux6.localdomain:9803/xmlpserver

OEM Console Screens

 OEM 13c Login Screen

 Accept the license agreement

 Select your home page based on your role. This can be changed later as well

 Middleware Management Screen

Thats it !! You now have a working OEM 13c environment.

Startup/Shutdown
Cloud Control is set to auto-start using the "gcstartup" service. The "/etc/oragchomelist"
file contains the items that will be started by the system.

/u01/app/oracle/middleware
/u01/app/oracle/agent/agent_13.1.0.0.0:/u01/app/oracle/agent/agent_inst

On a simple installation the default auto-start will cause a problem as Cloud Control will
attempt to start before the database has started. The service can be disabled by
commenting out (using #) all the contents of the "/etc/oragchomelist" file to prevent the
auto-start and use start/stop scripts described below.

If the start/stop needs to be automated, you can do it in the usual way using Linux
service that calls your start/stop scripts that include the database management.

Use the following commands to turn on all components installed by this article.

#!/bin/bash
export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1
export OMS_HOME=/u01/app/oracle/middleware
export AGENT_HOME=/u01/app/oracle/agent/agent_13.1.0.0.0
# Start everything
$ORACLE_HOME/bin/dbstart $ORACLE_HOME

$OMS_HOME/bin/emctl start oms

$AGENT_HOME/bin/emctl start agent

Use the following commands to turn off all components installed by this article.

#!/bin/bash
export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1
export OMS_HOME=/u01/app/oracle/middleware
export AGENT_HOME=/u01/app/oracle/agent/agent_13.1.0.0.0

# Stop everything
$OMS_HOME/bin/emctl stop oms -all

$AGENT_HOME/bin/emctl stop agent

$ORACLE_HOME/bin/dbshut $ORACLE_HOME

For more information see:

 Oracle Enterprise Manager Cloud Control 13c Post-Installation Setup Tasks

 Upgrade Oracle Enterprise Manager Cloud Control 12c Release 5 (12cR5) to 13c
Release 1 (13cR1)
 Enterprise Manager Cloud Control Basic Installation Guide 13c Release 1 (13.1.0.0)

http://dbaocm.blogspot.co.uk/2015/12/oracle-enterprise-manager-13c-r1.html
http://dbakevlar.com/2016/01/installing-a-new-enterprise-manager-13c-environment/

Installing User Ensure that you meet the following requirements:

Requirements
■ (For UNIX only) The installation must NOT be run by a root user.
■(For Microsoft Windows only) User must be part of the ORA-DBA
group and have administrator permissions.
■(For Microsoft Windows only) User must belong to the DBA
group, and have permissions to perform the following: Act as part
of the operating system, Create a token object, Log on as a batch
job, and Adjust memory quotas for a process.
To verify whether the install user has these rights, from the
Start menu, click Settings and then select Control Panel. From the
Control Panel window, select Administrative Tools, and from the
Administrative Tools window, select Local Security Policy. In the
Local Security Settings window, from the tree structure, expand
Local Policies, and then expand User Rights Assignment.

Due insufficient memory (SGA) there was a concurrency on database for a small
interval of time and same has been updated to Shaun. Once we will have a down time
for CRPRD database we address this issue.
On Microsoft Windows:
netstat -an|findstr <port_no>
To invoke the installation wizard on UNIX platforms, run
em13100_<platform>.bin. To invoke on Microsoft Windows
platforms, run setup_em_win64.exe.
■The installer requires about 10 GB of hard disk space in the
temporary directory. If your temporary directory does not have this
space, then pass the -J-Djava.io.tmpdir parameter and
provide an alternative directory where there is 10 GB of space.
The directory specified by this parameter will also be used as
the location for the Provisioning Advisor Framework (PAF) staging
directory, which is used for copying the Software Library entities
related to the deployment procedures. The PAF staging directory is
used only for provisioning activities — entities are copied for a
deployment procedure, and then, deleted once the deployment
procedure ends.
For example,
./em13100_linux64.bin -J-
Djava.io.tmpdir=/u01/software/em13c/stage/

■Ensure that there are no white spaces in the name of the directory
where you download and run the Enterprise Manager Cloud
Control software from. For example, do not download and run the
software from a directory titled EM Software because there is a

white space between the two words of the directory name.