Oracle Enterprise Manager 12c Installation 07-16-14

Mokum is the only full-time Oracle virtualization
integrator with the expertise to help you virtualize your

Production, Test and DR Oracle workloads.
sales@mokumsolutions.com
Copyright 2014 Mokum Solutions, Inc. All rights reserved.
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form
is prohibited unless prior permission is obtained from the Copyright holder.
About Mokum Solutions, Inc.
Founded in March 2011, Mokum Solutions, Inc. specializes in the implementation,
delivery and support of Oracle technologies in private and public clouds. Mokum
corporate headquarters are located in San Francisco, CA http://mokumsolutions.com
or call 1 415 252 9164
About the Author
The author of the Oracle Cloud Cookbook is none other than the owner of
Mokum Solutions, Inc., Roddy Rodstein. Roddy is one of the most respected
Oracle Cloud Computing experts, having designed and managed many of the
worlds largest and most complex Oracle private clouds. Before establishing
Mokum in March 2011, Roddy spent three years at Oracle on the Oracle VM
and Oracle Linux team designing and supporting Oracle's largest and most
complex customer environments. Before Oracle, Roddy spent six years at Citrix,
designing and supporting Citrix's largest and most complex customer environments,
Including Oracle's. With Mr. Rodsteins rich background and knowledge, there
can be no better resource for revealing the Oracle Cloud recipe.
Audience
The Oracle Cloud Cookbook is a comprehensive, field tested reference design that
guides you through each step to move to your Oracle software portfolio to an elastic
Oracle cloud using the Oracle VM product line, Oracle Linux, Oracle Engineered
Systems managed by Oracle Enterprise Manager 12c, with total control over Oracle
processor licensing.
http://mokumsolutions.com
Last update: 07/16/14

This document applies to Oracle Enterprise Manager 12c Release 4 installed on Oracle Linux or Red Hat Enterprise Linux 5 or 6 using the Oracle
Universal Installer (OUI).
Table of Contents
Oracle Enterprise Manager 12c Installation and Upgrades Introduction
Oracle Enterprise Manager 12c Inter Component Communication and Data Exchange
Oracle Enterprise Manager 12c System Design Considerations
Oracle Enterprise Manager 12c Server Sizing
Oracle Enterprise Manager 12c Release 4 Upgrade
Oracle Enterprise Manager 12c Linux Operating System Installation Prerequisites
Install the oracle-validated RPM on Oracle Linux 5
Install the oracle-validated RPM from the Oracle Public Yum Repository on Oracle Linux 5
Install the oracle-rdbms-server preinstall on Oracle Linux 6
Install the oracle-validated or oracle-rdbms-server preinstall RPM from the Oracle Linux DVD
Disable iptables
Disable SELinux
Congure the /etc/hosts File
Congure SSH and X11 Forwarding
Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation Prerequisites
Create the Required Directories using the Optimal Flexible Architecture (OFA) Standard
Adjust the Shared Memory File System for the Database Host
Congure the ulimit /etc/security/limits.conf Values
Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation
Automate the Oracle Database Startup and Shutdown
Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation Prerequisites
Download and Stage the Database Software
Create the Required Directories using the Optimal Flexible Architecture (OFA) Standard
Congure the ulimit, /etc/security/limits.conf and /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf Values
As the Installing User, Setup ~/.bash_prole
Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation
Post Installation Steps
Oracle Enterprise Manager 12c R4 Installation
Congure the .bash_prole File with the Oracle Environment Variables (Oracle 11gR2 DB)
Change Log
Revision
Change Description
Updated By
Date
1.0
Document Creation
Roddy Rodstein
12/02/11
1.1
Oracle Enterprise Manager 12c Release 1 Updates
Roddy Rodstein
09/27/12
1.2
Roddy Rodstein
05/06/13
1.3
Roddy Rodstein
09/02/13
1.4
Content Refresh
Roddy Rodstein
01/05/14
1.5
Roddy Rodstein
07/16/14
Oracle Enterprise Manager 12c Installation and Upgrades Introduction

Oracle Enterprise Manager 12c is a systems management framework consisting of an Oracle database, Oracle WebLogic, a J2EE application, an
application development frame work 11g (ADF) administrative Web GUI, server and client side plug-ins, and a client side agent. In the context of
Oracle Enterprise Manager, the Oracle database repository is named the Oracle Management Repository or OMR. WebLogic is the J2EE
platform called the Oracle Management Service or OMS, that runs the Oracle Enterprise Manager 12c J2EE application. The administrative
Web GUI is named Oracle Enterprise Manager Cloud Control. The client side agents are named the Oracle Management Agents or OMA. The
server and client side plug-ins share a unique name for the managed product or technology. Monitored hosts are referred to as targets. All of the
Oracle Enterprise Manager components are commonly referred to as Oracle Enterprise Manager (OEM) or Enterprise Manager (EM).
The Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a single
x86-64 Linux host in an all-in-one conguration or in an n-tier conguration. Traditionally, production Oracle Enterprise Manager environments
are not be placed on a single server, nor should the Oracle Management Repository be shared with production or test databases on the same
server. For production, the Oracle Management Repository as well as WebLogic should be on dedicated virtual or physical servers. If your Oracle
Enterprise Manager environment starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager infrastructure.
Each of the Oracle Enterprise Manager 12c components can be installed using the Oracle Universal Installer (OUI) GUI, or using silent
installation scripts, or with the software only, congure later installation mode. The software only installation mode allows you to install only the
Oracle Enterprise Manager software binaries without any congurations. The software only installation mode is ideal if you want to install the
software at one point and congure the software later.
Mokum Solutions, Inc. +1 415 252-9164
4 of 52
Figure 1 shows an all-in-one Oracle Enterprise Manager 12c installation with the Oracle Management Repository and the Oracle Management
Service on a single Linux node with three managed Oracle Linux hosts. All-in-one Oracle Enterprise Manager 12c installations are ideal for
evaluations.
Figure 2 shows a multiple node Oracle Enterprise Manager 12c installation with the Oracle Management Repository on one Linux node, the
Oracle Management Service on a second Linux node with three managed Oracle Linux hosts. Multiple node Oracle Enterprise Manager 12c
installations are ideal for small, medium and large sites.
Figure 3 shows a high availability Oracle Enterprise Manager 12c installation with the Oracle Management Repository on a two node Linux RAC
cluster, the Oracle Management Service on two load balanced Linux nodes with three managed Oracle Linux hosts. High availability Oracle
Enterprise Manager 12c installations are ideal for medium and large sites.
5 of 52
There are several Oracle Enterprise Manager Cloud Control 12c Release 4 Installation and Upgrade options.
1. The rst option is a fresh installation using the Oracle Enterprise Manager Cloud Control 12c Release 4 installation media.
2. The second option for Oracle Enterprise Manager on Release1 (12.1.0.1+BP1) or Release 2 (12.1.0.2), or on older releases 11g and 10.2.0.5,
is to download the Oracle Enterprise Manager Cloud Control 12c Release 4 installation media, then upgrade directly to Oracle Enterprise
Manager Release 4.
As of this writing, Oracle Enterprise Manager 12c Release 1 (12.1.0.1) up to Release 2 (12.1.0.4) are supported on the following Oracle Linux and
Red Hat Enterprise Linux x86-64 operating systems:
Oracle Linux and Red Hat Enterprise Linux 6+ (all 6 releases, i.e. 6.0 through 6U5)
Oracle Linux and Red Hat Enterprise Linux 5+ (all 5 releases, i.e. 5.0 through 5U10)
As of this writing, the Oracle Management Repository is certied with the following database releases for Oracle Linux 5 and 6, x86_64:
12.1.0.1.0
11.2.0.4.0
11.2.0.3.0
11.2.0.2.0
11.2.0.1.0
11.1.0.7.0
10.2.0.5.0
Oracle Enterprise Manager 12c Inter Component Communication and Data Exchange
Oracle Enterprise Manager 12c Could Control, the Oracle Management Repository, the Oracle Management Service and the Oracle Management
Agents and Plug-ins can be on dierent hosts throughout your enterprise. Understanding Oracle Enterprise Manager's intra component
communication and data exchange will help you congure your rewalls in order to allow Oracle Enterprise Manager to operate in your
enterprise. During the Oracle Enterprise Manager installation, the default communication ports for each component will be selected and
assigned. If the default ports are modied be sure to use the new port assignments when you congure your rewalls.
Table 1 shows the default ports used by Oracle Enterprise Manager.
Service
Default Port
Enterprise Manager Upload HTTP Port
4889 - 4898
Enterprise Manager Upload HTTPS (SSL) Port
1159, 4899 - 4908
Management Agent Port
3872
Management Repository Database Port
1521
Cloud Control Console HTTP Port
7788 - 7798
Cloud Control Console HTTPS (SSL) Port
7799 -7809
EM Domain WebLogic Admin Server HTTP Port
7001
EM Domain WebLogic Admin Server HTTPS (SSL)

Port
7101 - 7200
6 of 52
Service
Default Port
Cloud Control Managed Server HTTP Port
7201 - 7300
Cloud Control Managed Server HTTPS (SSL) Port
7301 - 7400
WebLogic Node Manager HTTPS (SSL) Port
7401 - 7500
JVM Diagnostics Managed Server
3800
JVM Diagnostics Managed Server (SSL)
3801
Application Dependency and Performance RMI

Registry Port
51099
Application Dependency and Performance Java

Provider Port
5503
Application Dependency and Performance Remote

Service Controller Port
55000
Oracle Enterprise Manager 12c System Design Considerations

The Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a single host
in an all-in-one conguration or in an n-tier conguration. Traditionally, small Oracle Enterprise Manager environments are hosted on a single
server, and large and medium Oracle Enterprise Manager environments are set-up in an n-tier conguration with the Oracle Management
Repository as well as the Oracle Management Service (WebLogic) on dedicated virtual or physical servers. If your Oracle Enterprise Manager
environment starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager infrastructure.
For the Oracle Management Repository, scaling out means moving to RAC for the Oracle Management Repository database. An important
consideration when scaling out an Oracle Enterprise Manager environment, is to determine if the underlying hardware where the Oracle
Management Repository database runs is capable to transition to RAC? If the hardware is not capable to transition to RAC, it is possible to move
and/or export the Oracle Management Repository database to a dierent system with more resources. If the Oracle Management Repository is
hosted on an Oracle VM virtual machine, transitioning to RAC is a trivial operation.
Scaling out the WebLogic and Oracle Management Service tier entails adding a load balancing (SLB) solution to front end multiple WebLogic
servers hosting the Oracle Management Service. Adding a load balancer with additional WebLogic servers introduces a virtual host name for the
WebLogic cluster. Introducing a virtual host name into an existing Oracle Enterprise Manager environment will require a reconguration of all of
your Oracle Management Agents to resolve to the new virtual host name. Reconguring a couple Oracle Management Agents is no trouble,
although reconguring a lot of Oracle Management Agents would demand a long service window. When you deploy Oracle Enterprise Manager,
consider using a virtual host name for the web tier.
An additional consideration when scaling out the WebLogic and Oracle Management Service tier is to provision shared storage to hosts the XML
les and the software library.
Oracle Enterprise Manager 12c Server Sizing

Oracle Enterprise Manager 12c server sizing is calculated by a) total number of managed agents and targets, b) the future growth of your Oracle
Enterprise Manager environment and c) your organization's high availability requirements. For example, if you know the total number of
managed agents and targets, sizing WebLogic and the Oracle database is as simple as following Table 1, Table 2, and Table 3. As you add more
agents and targets, it is important to consider the future growth of your Oracle Enterprise Manager environment as well as the ability to scale up
or to scale out with additional CPU, RAM and storage.
Table 1 shows the recommended Oracle Enterprise Manager hardware requirements for an evaluation, small, medium and large deployment.
Deployment Size
OMS Hosts
OMS CPU
Cores
OMS
RAM
DB
Hosts
DB CPU
Cores
DB
RAM
All-in-one
Install Recommendation
Eval < 10 agents < targets
*4 GB
Yes
Small < 100 agents < 1000

targets
*6 GB
No
Medium < 1000 agents <

10,000 targets
*6 GB
1 or 2
*2 with
RAC
4
4 for each RAC
node
No
Large > 1000 agents >

10,000 targets
*6 GB
2
*2 with
RAC
8 for each RAC

node
16
No
* To use BI Publisher add 1.5 GB of RAM.

Table 2 shows the minimum storage requirments for the database server hosting the Oracle Management Repository.
Deployment Size
MGMT_TABLESPACE (GB) MGMT_ECM_DEPOT_TS (GB) TEMP ARCHIVE LOG AREA (GB)

Small < 100 agents < 1000 targets
Medium < 1000 agents < 10,000 targets
15 GB
50 GB
10
25
200 GB
20
100
7 of 52
Deployment Size
MGMT_TABLESPACE (GB) MGMT_ECM_DEPOT_TS (GB) TEMP ARCHIVE LOG AREA (GB)

Large > 1000 agents > 10,000 targets
15 GB
300 GB
40
150
Table 4 shows the minimum storage requirements for a standalone Oracle Management Agent installation.
Platform
Storage
TMP Directory
Linux 32 bit
1.2 GB
400 MB
Linux x86_64
1.2 GB
400 MB
Oracle Enterprise Manager 12c Release 4 Upgrade

This section describes how to upgrade Oracle Enterprise Manager 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3) to 12c Release 4
(12.1.0.4). Before starting the Release 4 upgrade, it is necessary to meet several database and operating system prerequisites.
1) First, apply the appropriate Database patch(s) to the Oracle Management Repository database.
Table 5 shows the Database patch matrix:
Oracle Database Release
Patches
Oracle Database 11 Release 1 (11.1.0.7)
On Linux apply patch 17082366 (Patch Set Update 17), then apply patch 9577583,
and patch 8405205.
Oracle Database 11g Release 2 (11.2.0.1)
On Linux apply patch 12419378 (Patch Set Update 6).
Oracle Database 11g Release 2 (11.2.0.2)
On Linux apply patch 11061801 and patch 9748749.
Oracle Database 11g Release 2 (11.2.0.3), 10g Release 2

On Linux apply patch 11061801.
(10.2.0.5)
Oracle Database 12c Release 1 (12.1.0.1)
On Linux apply patch 16619249, and patch 13496395.
Note: Consult the patch README for the Database patch installation details.
2) Conrm that the privileges for the DBMS_RANDOM package meets Oracle's prerequisites. As the installing user, i.e. the user account used to install the Oracle database, set the
following environment variables.
$
$
$
$
export ORACLE_SID=<MY SID>

export ORAENV_ASK=NO
. oraenv
export ORAENV_ASK=YES
# sqlplus / as sysdba
GRANT EXECUTE ON dbms_random TO dbsnmp;
GRANT EXECUTE ON dbms_random TO sysman;
REVOKE EXECUTE ON dbms_random FROM public;
3) Conrm that there are no invalid objects in the Oracle Management Repository database.
SELECT owner, object_name, object_type
FROM dba_objects
WHERE status = 'INVALID'
AND owner IN ('SYS', 'SYSTEM', 'SYSMAN', 'MGMT_VIEW', 'DBSNMP', 'SYSMAN_MDS');
If you need to recompe, the following examples show the syntax:
EXEC UTL_RECOMP.recomp_serial('SYS');
EXEC UTL_RECOMP.recomp_serial('DBSNMP');
EXEC UTL_RECOMP.recomp_serial('SYSMAN');
4) Conrm that the "/etc/security/limits.conf" le has the number of le descriptors to at least 4096. As root, edit the /etc/security/limits.conf le
and conrm that the following line exists:
oracle soft nole 4096
5) Backup the Oracle Management Repository database.
6) Copy the emkey using the following commands. The WebLogic user account name and password will be required to copy the emkey. Change
the path, hostname, and database SID to meet your requirments.
$ export OMS_HOME=/u01/app/oracle/product/Middleware/oms
$ OMS_HOME/bin/emctl cong emkey -copy_to_repos_from_le -repos_host <MY HOSTNAME> -repos_port 1521 -repos_sid <MY SID>
-repos_user sysman -emkey_le $OMS_HOME/sysman/cong/emkey.ora
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
Enter Admin User's Password :
Enter Enterprise Manager Root (SYSMAN) Password :
The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure.
After the required operation has been completed, secure the EMKey by running "emctl cong emkey -remove_from_repos".
$
8 of 52
7) Stop the Oracle Management Service.
$OMS_HOME/bin/emctl stop oms -all
8) Create a directory for the out-of-place Oracle Management Service upgrade.
$ mkdir -p /u01/app/oracle/product/MiddelwareR4
9) Unzip the Oracle Enterprise Manager R4 software into a staging directory. Change the path to meet your requirments.
$ mkdir -p /u01/app/oracle/product/MiddelwareR4
$ unzip -d /u01/scratch em12104_linux64_disk1.zip
$ cd /u01/app/oracle/oms12cr4
10) Run the Oracle Universal Installer (OUI) to begin upgrade.
$ cd /u01/scratch
$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 400 MB. Actual 12133 MB Passed
Checking swap space: must be greater than 150 MB. Actual 14322 MB Passed
Checking monitor: must be congured to display at least 256 colors. Actual 16777216 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-06-24_05-30-24AM. Please wait
$
After a couple moments, the Oracle Universal Installer will appear and show Step 1 or 9, the My Oracle Support Details screen.
My Oracle Support Details screen
On the My Oracle Support Details screen to receive information from Oracle (optional), enter your email address, select the I wish to receive
security updates via My Oracle Support checkbox, enter your My Oracle Support Password and click the Next button, or uncheck the I
wish to receive security updates via My Oracle Support checkbox and click the Next button.
Figure 4
Software Updates screen

On the Software Updates screen select one of the following software update options, then click Next to proceed:
Skip to Skip looking for updates
Search for Updates (Prerequisites, Critical Patches, Interim Patches, etc.)
Local Directory (select this option if you have allready pulled down the Prerequisites, Critical Patches, Interim Patches, etc.)
My Oracle Support (select this option to search My Oracle Support for the Prerequisites, Critical Patches, Interim Patches, etc.)
For this example we selected Search for Updates, and My Oracle Support, entred a User Name and Password, then clicked Search for
Updates, there were no updates. Click the Next button to proceed.
Figure 5
9 of 52
Prerequisite Checks screen

On the Prerequisite Checks screen the installer checks the system prerequisites. Failed steps can be xed and be retested or just
ignored. The Prerequisite Checks screen shows if the minimum system requirements to perform the installation are met.
Click Rerun if you xed the problems and you would like to verify the system requirements again.
Click Ignore to ignore the problems and move forward with the upgrade.
Click the Next button to proceed.
Figure 6
Installation Types screen

On the Installation Types screen select Upgrade and One System Upgrade. The existing Middelware home should automataically seletced.
Figure 7
10 of 52
Installation Details screen

On the Installation Details screen enter the new R4 Middleware home. Use the Browse button to select, or type in the R4 Middleware Home
Location path. The Host Name should auto-populate. If the hostname does not auto-populate, enter the fully qualied domain name (FQDN) of
the host.
Figure 8
Database Connection Details screen

On the Database Connection Details screen enter the Database SYS and SYSMAN Passwords, select the Confrim that you have backed
up the Management Repository checkbox. Click the Next button to proceed.
Figure 9
11 of 52
Error screen
On the Error screen click Yes to automatically fix the issues and proceed.
Figure 10
Plug-ins Upgrade screen

On the Plug-ins Upgrade screen accept the defaults and click Next to proceed.
Figure 11
12 of 52
Select Plug-ins screen

On the Select Plug-ins screen select any additional Plug-ins. Click the Next button to proceed.
Figure 12
Extend WebLogic Server Domain screen

On the Extend WebLogic Server Domain screen enter the Admin Server Host name, Admin Server Port, WebLogic User
Name and Password. The OMS Instance Base Location should auto-populate. Click the Next button to proceed.
Figure 13
13 of 52
Review screen
On the Review screen conrm the installation setting and continue if correct. Click the Install button to proceed with installation.
Figure 14
Installation Progress Details screen

On the Installation Progress Details screen you can monitor the progress of the installation until user input is required.
Figure 15
14 of 52
Execute Conguration scripts screen

As requested on the Execute Conguration scripts screen, as the root user, run the allroot.sh script.
Figure 16
# /u01/app/oracle/product/MiddlewareR4/oms/allroot.sh
Starting to execute allroot.sh .........
Starting to execute /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/MiddlewareR4/oms
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Entries will be added to the /etc/oratab le as needed by
Database Conguration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specic root actions will be performed.
/etc exist
Creating /etc/oragchomelist le...
/u01/app/oracle/product/MiddlewareR4/oms
Finished execution of /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......
Starting to execute /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......
Finished product-specic root actions.
15 of 52
Finished execution of /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......
#
Once the Installation Progress Details screen shows 100%, you will be preseneted with the FInish screen.
Figure 17
Finish screen
The Finish screen shows the location of the setupinfo.txt le and the URLs for Oracle Enterprise Manager Cloud Control and the WebLogic
Admin server. Click the Close button to close the installation program
Note: The details from the Finish screen are also available in the le setupinfo.txt le.
Figure 18
The following is an example of the setupinfo.txt le from this install.
16 of 52
$ cat /u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txt
This information is also available at:
/u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
Use the following URL to access:
1. Enterprise Manager Cloud Control URL: https://oem-sisko.local.mokumsolutions.com:7802/em
2. Admin Server URL: https://oem-sisko.local.mokumsolutions.com:7102/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: oem-sisko.local.mokumsolutions.com
2. Admin Server Port: 7102
You can nd the details on ports used by this deployment at : /u01/app/oracle/product/MiddlewareR4/oms/install/portlist.ini
NOTE:
An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the
Repository becomes unusable.
A backup of the OMS conguration is available in /u01/app/oracle/product/gc_inst/em/EMGC_OMS1/sysman/backup on host
oem-sisko.local.mokumsolutions.com. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.
NOTE: This backup is valid only for the initial OMS conguration. For example, it will not reect plug-ins installed later, topology changes like the
addition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensure
they capture the current OMS conguration. Use the following command to backup the OMS conguration:
/u01/app/oracle/product/MiddlewareR4/oms/bin/emctl exportcong oms -dir <backup dir>
The upgrade is now complete and ready for login. You will be presneted with the Accessibility Preferance screen. Selct your Accessibility
Preferance or click I'll deal with this later to access Cloud Control.
Figure 19
Oracle Enterprise Manager 12c Linux Operating System Installation Prerequisites

Oracle recommends installing Oracle Linux and Red Hat Enterprise using the default software package selections without any customization.
Using the default software packages without customizations includes most of the prerequisite packages for Oracle Enterprise Manager 12c, and
helps limit the number of manual prerequisites. After an Oracle Linux and/or Red Hat Enterprise Linux installation, for 5+, install the oraclevalidated RPM, for 6+ install the oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall (dependent on db
version), to meet all of the remaining Oracle Enterprise Manager 12c software RPM prerequisites as well as the system conguration
prerequisites.
Install the oracle-validated RPM on Oracle Linux 5

The oracle-validated RPM simplies meeting the software and system conguration prerequisites for installing Oracle Enterprise Manager 12c.
Installing the oracle-validated RPM automatically installs all of the software RPM prerequisites for the Oracle Enterprise Manager 12c and the
Oracle Database as well as meeting the system conguration prerequisites, such as creating an oracle user and the oinstall and dba groups,
conguring the sysctl.conf settings, system startup parameters, user limits, and driver parameters.
17 of 52
The oracle-validated RPM is available at the Oracle Unbreakable Linux Network, on the Oracle Linux media, and from the Oracle public yum
repository. The oracle-validated RPM can be installed from the Oracle Unbreakable Linux Network by typing "up2date --install oracle-validated",
ULN registration and a valid Linux CSI is required. If you do not have access to Oracle Unbreakable Linux Network, the oracle-validated RPM
can be installed from a local DVD repository as well as from Oracle' public yum repository.
Install the oracle-validated RPM from the Oracle Public Yum Repository on Oracle Linux
5
To install the oracle-validated RPM from the Oracle public yum repository, as root type the following commands:
# cd /etc/yum.repos.d/
# wget http://public-yum.oracle.com/public-yum-el5.repo
# yum install oracle-validated
Note: The oracle-validated RPM is only for Oracle Linux 4 and 5, not 6. For Oracle Linux 6, install the oracle-rdbms-server preinstall RPM.
By default the public-yum-el5.repo le has the el5_latest RPM channel enabled. The Oracle public yum server latest RPM channel include the
base OS version installation RPM packages along with the latest software patches, updates and xes. Patch jobs using the latest RPM channel
update hosts to their respected latest version update with the latest software patches, updates and xes. A patch job executed on a Oracle Linux
5U5 host would update the host from 5U5 to 5U10 with the latest latest software patches, updates and xes. To keep a host at its respected
update level, a valid CSI and the Unbreakable Linux Network is required. With the Unbreakable Linux Network, it is possible to register a host
the el*/ol*_base channel along with the el*/ol*_patch RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch RPM
channels, the hosts are patched with the latest software patches, updates and xes from their respected update channel, i.e. 5, 5U1, 5U2 and
5U3, etc...
Note: If the host is not 5U10/latest, once the oracle-validated is installed, edit the public-yum-el5.repo le and disable the el5_latest RPM channel
by changing enabled=1 to enabled=0.
The next example shows the el5_latest entry from the public-yum-el5.repo le with the enabled=1 ag, i.e. the el5_latest RPM repository is
enabled.
[el5_latest]
name=Oracle Linux $releasever Latest ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/$basearch/
gpgkey=le:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
gpgcheck=1
enabled=1
deisabled.
[el5_latest]
gpgcheck=1
enabled=0
A good practice after the oracle-validated RPM installation is to set the password for the oracle user created during the script. As root, type the
following:
$ passwd oracle
Changing password for user oracle.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
$
Install the oracle-rdbms-server preinstall on Oracle Linux 6

The oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall (dependent on db version) RPM, formally know as
oracle-validated, simplies meeting the software and system conguration prerequisites for installing the Oracle Database, Oracle Enterprise
Manager, and many other Oracle technology products on Oracle Linux 6. Installing the oracle-rdbms-server-11gR2-preinstall or oraclerdbms-server-12cR1-preinstall RPM automatically installs all of the software RPM prerequisites for Oracle Database and Oracle Enterprise
Manager, as well as meeting the system conguration prerequisites, such as creating an oracle user and the oinstall and dba groups, conguring
the sysctl.conf settings, system startup parameters, user limits, and driver parameters. After the installation of the oracle-rdbms-server-11gR2preinstall or oracle-rdbms-server-12cR1-preinstall RPM, you can condently start the Oracle Database and Oracle Enterprise Manager
product installer. The oracle-rdbms-server-11gR2-preinstall and oracle-rdbms-server-12cR1-preinstall RPMs are available at the Oracle
Unbreakable Linux Network, on the Oracle Linux media, and from the Oracle public yum repository.
Note: A prerequisite for the oracle-rdbms-server-11gR2-preinstall and oracle-rdbms-server-12cR1-preinstall RPMs is the Unbreakable
Enterprise Kernel (UEK).
To install the oracle-rdbms-server preinstall RPM from the Oracle public yum repository, as root type the following commands:
# cd /etc/yum.repos.d/
# wget http://public-yum.oracle.com/public-yum-ol6.repo
Install the oracle-rdbms-server-12cR1-preinstall package as the root user:
# yum install oracle-rdbms-server-12cR1-preinstall
18 of 52
Install the oracle-rdbms-server-11gR2-preinstall package as the root user:
# yum install oracle-rdbms-server-11gR2-preinstall
By default the public-yum-ol6.repo le has the ol6_latest RPM channel enabled. The Oracle public yum server latest RPM channel include the
base OS version installation RPM packages along with the latest software patches, updates and xes. Patch jobs using the latest RPM channel
update hosts to their respected latest version update with the latest software patches, updates and xes. A patch job executed on a Oracle Linux
6U1 host would update the host from 6u1 to 6U5 with the latest latest software patches, updates and xes. To keep a host at its respected update
level, a valid CSI and the Unbreakable Linux Network is required. With the Unbreakable Linux Network, it is possible to register a host the
el*/ol*_base channel along with the el*/ol*_patch RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch RPM channels,
the hosts are patched with the latest software patches, updates and xes from their respected update channel, i.e. 6, 6U1, 6U2 and 6U3, etc...
Note: If the host is not 6U5/latest, once the oracle-rdbms-server preinstall is installed, edit the public-yum-ol6.repo le and disable the el6_latest
RPM channel by changing enabled=1 to enabled=0.
enabled.
[ol6_latest]
gpgcheck=1
enabled=1
disabled.
[ol6_latest]
gpgcheck=1
enabled=0
A good practice after the rdbms-preinstall RPM installation is to set the password for the oracle user created during the script. As root, type the
following:
$ passwd oracle
New password:
$
Install the oracle-validated or oracle-rdbms-server preinstall RPM from the Oracle

Linux DVD
Linux maintains yum repositories in the /etc/yum.repos.d/ directory. For example, to setup a DVD repository, mount the Oracle Linux DVD ISO le,
and create a le in the /etc/yum.repos.d/<MY FILE>.repo directory that instructs the yum client to use the DVD repository. The next examples
shows the syntax of a .repo le pointing to a mounted Oracle Linux DVD in the /mnt/dvd/ directory.
# cat /etc/yum.repos.d/ol-5U7-dvd.repo
[ol5_u7_dvd]
name=Oracle Linux $releasever - $basearch
baseurl=le:///mnt/dvd/Server/
enabled=1
gpgcheck=1
Note: Change the folloiwing sections to meet you DVD requirments:
Change the name of the .repo le. For example, for 5U10, ol-5U10-dvd.repo, or for 6U5, ol-6U5-dvd.repo.
Change the name of the respitory [ol5_u7_dvd] to meet your requirments, i.e. for 5U10, [ol5_u10_dvd], or for 6U5, [ol6_u5_dvd].
Replace baseurl=le:///mnt/dvd/Server/ with your DVD mount point.
Once the DVD is mounted and the <MY FILE>.repo le is created, as root type the following command:
# yum install oracle-validated (For Oracle Linux 5)
or
# yum install oracle-rdbms-server-11gR2-preinstall (for Oracle Linux 6)
or
# yum install oracle-rdbms-server-12cR1-preinstall (for Oracle Linux 6)
A good practice after the rdbms-preinstall RPM installation is to set the password for the oracle user created during the script. As root, type the
following:
$ passwd oracle
New password:
$
19 of 52
Disable iptables
iptables is a userspace rewall application used to congure the Linux IPv4 and IPv6 packet ltering rulesets. iptables is installed and enabled by
default on Oracle Linux with a default policy and ruleset in /etc/syscong/iptables. iptables rules can be congured at the command line as well as
with the system setup utility, i.e. "/usr/bin/setup".
Host rewalls, for example iptables, are a fundamental part of an information security program. If your information security program requires
host rewalls, a best practice is to congure host rewalls during the last phase of the Enterprise Manager deployment.
iptables can be disabled by typing the following command as root.
# service iptables stop && service ip6tables stop && chkcong iptables o && chkcong ip6tables o
iptables can be re-inabled by typing the following command as root.
# service iptables start && service ip6tables start && chkcong iptables on && chkcong ip6tables on
Disable SELinux
Security Enhanced Linux (SELinux) is a default Linux feature that oers mandatory access controls, using Linux kernel security modules (LSM)
along with user-space tools. Starting with Oracle Database 11g Release 2 (11.2), Security Enhanced Linux is supported for Oracle Linux 4, Red
Hat Enterprise Linux 4, Oracle Linux 5, and Red Hat Enterprise Linux 5. Security Enhanced Linux is not supported for the Oracle Enterprise
Manager 12c Oracle Management Service.
Mandatory access controls, for example Security Enhanced Linux, may be a part of your organizations information security program. If your
information security program requires mandatory access controls for the 12c Oracle Management Repository, a best practice is to congure
Security Enhanced Linux during the last phase of the Enterprise Manager deployment.
To conrm the status of SELinux, as root type sestatus as shown in the next example.
# sestatus
SELinux status:
disabled
The above example shows a host with SELinux disabled.
Security Enhanced Linux can be temporarily disabled by typing "echo 0 > /selinux/enforce", as root. Security Enhanced Linux can be re-enabled
by typing "echo 1 > /selinux/enforce", as root.
Security Enhanced Linux can be permanently disabled by changing the "SELINUX=enforcing" entry to "SELINUX=disabled" in the "/etc/selinux
/cong" le. Security Enhanced Linux can be re-enabled by changing the "SELINUX=disabled" entry to "SELINUX=enforcing" in the "/etc/selinux
/cong" le. A re-boot is required after changing the "SELINUX= value to enable to new settings.
Congure the /etc/hosts File

Oracle technology products, including Oracle Enterprise Manager, rely on a properly formatted /etc/hosts le which allows the host to be
pingable, with long and short host names. The host name in the /etc/hosts le must be associated with the server's public IP address.
The next example shows the proper syntax from a /etc/hosts le. Note that the localhost entries are one one line, and the IP address with the long
and short names are on the next line.
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
The next example shows an improperly formatted /etc/hosts le. Note that the long and short names are on the same line as the localhost entries.
127.0.0.1 servername.com servername localhost.localdomain localhost
Tip: The following IPv6 entries in Oracle Linux 5 & 6 /etc/hosts les should be removed to aviod "Bug 13652664 : AGENT DEPLOY FAILS WITH
AGENT PORT PASSED BY USER IS BUSY" with Oracle Management Agent installations:
::1
localhost localhost.localdomain localhost6 localhost6.localdomain6
The /etc/hosts le can be edited by the root user bu typing vi /etc/hosts, as shown in the next example.
# vi
127.0.0.1 localhost.localdomain localhost
:wq!
Congure SSH and X11 Forwarding

Installing the Oracle Enterprise Manager 12c components using the Oracle Universal Installer (OUI) GUI requires local or remote access to the
server' console or a remote X Windows (X11) session. Please note that the only software requirements on the Linux Oracle Enterprise Manager
host for remote X Windows (X11) sessions is the xauth RPM package. The xauth RPM package handles the X11 forwarding authentication.
X-windows and xhost are not required on the Linux Oracle Enterprise Manager host for remote X Windows (X11) sessions.
SSH and X11 forwarding enables the redirection of an X11 session from a remote Oracle Linux machine to a local desktop. For example, from a
local desktop, ssh to a remote Oracle Linux server using X11 forwarding and run the Oracle Universal Installer, i.e. by typing ./runInstaller. The
20 of 52
Oracle Universal Installer will be displayed on the local desktop and the Oracle Enterprise Manager 12c components can be installed on the
remote Oracle Linux server.
On the Oracle Linux server, enable X11 forwarding in the /etc/ssh/sshd_cong by adding "ForwardX11 yes" to the le as shown in the next
example.
Change
#X11Forwarding no
To
X11Forwarding yes
Once the "ForwardX11 yes" entry has been added to the /etc/ssh/sshd_cong le, restart ssh by typing "service sshd restart" to enable X11
forwarding. With X11 forwarding enabled, the Oracle Universal Installer (OUI) GUI can be exported from the Oracle Linux server to your local
desktop.
Tip: To aviod X11 challanges install the xauth and xorg-x11-apps RPMs on the Linux host. To check for the RPMs, as root type, rpm -qa | grep -i
xauth and rpm -qa | grep -i xorg-x11-apps. To install xauth and the xorg-x11-apps RPMs, type yum -y install xorg-x11-apps xauth.
To enable X11 forwarding from a Linux desktop, use the "-X" switch with ssh. For example, type "ssh -X oracle@<ORACLE LINUX SERVER>" to
create a ssh tunnel with X11 forwarding. Do not forget that -X enables X11 forwarding, and -x actually disables X11 forwarding. Also, using the su
command within a SSH session with X11 forwarding breaks X11 authentication.
To test remote X Windows (X11), open a new ssh session with X11 forwarding enabled (ssh -X user@servername), and type xclock. The xclock
application should open on your desktop. xclock is an X window client application that is included in the xorg-x11-apps RPM package. xclock is
often used to test remote X Windows (X11) sessions.
Tip: To troubleshoot ssh connections, use ssh verbose mode, i.e. ssh -v -v -X user@servername
If your using a Windows PC, a PC X Server like XMing is required to run an X Windows session, along with an ssh client like putty that supports
X11 forwarding.
If you get X11 forwarding request failed on channel 0 messages from an ssh connection, on the target Oracle Linux server edit the /etc/ssh/sshd_config file,
and ensure that "X11Forwarding yes" is not commented, add "X11UseLocalhost no", and uncomment "AddressFamily any". Next, restart sshd by typing "service sshd
restart", and your X11 apps will successfully run.
Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation Prerequisites

Before starting the Oracle Database 11g R2 installation, it is necessary to meet several database, and operating system prerequisites, and to create the installation directories.
Create the Required Directories using the Optimal Flexible Architecture (OFA)
Standard
The Optimal Flexible Architecture (OFA) standard is a set of le naming recommendations for managing Oracle installations. The Optimal Flexible
Architecture standard oers mount point, directory, and le-naming conventions that work with the Oracle Universal Installer. The Optimal
Flexible Architecture includes where to install each part of each Oracle product including the storage of the applications and the data.
To create the directories for Oracle software installation using the Optimal Flexible Architecture standard, as root, type the following:
# mkdir -p /u01/app/oracle/product/
# chown -R oracle:oinstall /u01
# chmod -R 775 /u01
Adjust the Shared Memory File System for the Database Host
To meet the Oracle Management Repository conguration requirements, the shared memory le system size should be increased to 4 GB.
Note: The shared memory le system size needs to be increased only on the Database host.
To check the current size of the shared memory le system, type df -k /dev/shm as shown in the next example.
# df -k /dev/shm
Filesystem
1K-blocks
tmpfs
3056052
Used Available Use% Mounted on

0 3056052 0% /dev/shm
The above examples shows a 3 GB shared memory le system.

To set the shared memory le system size to 4 GB, as root, type the following commands.
# umount tmpfs
# mount -t tmpfs shmfs -o size=4g /dev/shm
Next, add the following entry in /etc/fstab to automatically mount the 4 GB shared memory le system.
tmpfs
/dev/shm
tmpfs size=4g
00
Congure the ulimit /etc/security/limits.conf Values

One of the Oracle Enterprise Manager 12c installation prerequisites is to increase the number of le descriptors to at least 4096. As root, edit
21 of 52
the /etc/security/limits.conf le and add the following two entries:
<UID> soft nole 4096
<UID> hard nole 4096
Conrm the new le limits by typing:
$ ulimit -n
and
$ /bin/sh -c "ulimit -n"
The value should be greater than 4096.
Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation

This section walks through the installation of Oracle Database 11g Release 2 (11.2.0.4.0) using the Oracle Universal Installer (OUI) on Oracle
Linux 5 or 6.
With the software downloaded and staged on the Oracle Linux host, as the installing user, i.e. oracle, run the runInstaller script by typing
"./runInstaller" as shown in the next example.
# ssh -X oracle@<DATABASE HOST>
$ cd /u01/app/stage/database
$ ./runInstaller
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-11-30_04-53-29PM. Please wait ...
On the Congure Security Updates screen, to receive information from Oracle (optional), enter your email address and My Oracle Support
password and click the Next button, or uncheck the I wish to receive security updates via My Oracle Support checkbox and click the Next
button.
Figure 20
On the Download Software Updates screen, select one of the following three software update options, then click Next to proceed:
Use My Oracle Support credentials for download
Use pre-downloaded software updates
Skip software updates
For this example we selected the Skip software updates option and then Next to proceed.
Figure 21
22 of 52
On the Select Install Option screen, select Create and congure a database. Click the Next button to proceed.
Figure 22
On the System Class screen, select the Server Class option. Click the Next button to proceed.
Figure 23
23 of 52
On the Grid Installation Options screen, select the Single instance database installation option. Click the Next button to proceed.
Figure 24
On the Select Install Type screen, select the Tipical install option. Click the Next button to proceed.
Figure 25
24 of 52
On the Typical Install Conguration screen, accept the defaults, enter a Administrative password. Click the Next button to proceed.
Figure 26
On the Create Inventory screen, accept the defaults. Click the Next button to proceed.
Figure 27
25 of 52
The Perform Prerequisite Checks screen shows if the minimum system requirements to perform the database installation are met.
Click Check Again, if you xed the problems and you would like to verify the system requirements again.
Click Fix & Check Again, if you want the installer to try to x the problems and verify the system requirements again.
Click Ignore All to ignore the problems and move forward with the database installation.
Figure 28
On the Summary screen, click the Install button to start the database installation.
Figure 29
26 of 52
The Database Conguration Assistant screen shows the progress of the database conguration.
Figure 30
The second Database Conguration Assistant screen shows the database congurations. Click the OK button to close the Database
Conguration Assistant screen.
Figure 31
27 of 52
The Execute Conguration script screen appears and shows what scripts needs to be executed as the root user. As the root user, open a
terminal and run both of the root.sh scripts. Next, click OK to close the Execute Conguration script screen.
Figure 32
The Finish screen shows the Enterprise Manager Database Control URL. Click the Close button to close the installation program
Figure 33
28 of 52
Next, as the oracle user drop Enterprise Manager Database Control by typing the following command. Substitute <sys pasword> with the
sys password and <sysman password> with the sysman password selected during the database installation.
$ $ORACLE_HOME/bin/emca -decong dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
STARTED EMCA at Nov 22, 2011 1:44:08 PM
EM Conguration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: orcl
Listener port number: 1521
Do you wish to continue? [yes(Y)/no(N)]: Y
Nov 22, 2013 1:44:23 PM oracle.sysman.emcp.EMCong perform
INFO: This operation is being logged at /u01/app/oracle/product/cfgtoollogs/emca/orcl/emca_2013_11_22_13_44_08.log.
Nov 22, 2013 1:44:23 PM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Nov 22, 2013 1:44:45 PM oracle.sysman.emcp.EMReposCong invoke
INFO: Dropping the EM repository (this may take a while) ...
Nov 22, 2013 1:47:18 PM oracle.sysman.emcp.EMReposCong invoke
INFO: Repository successfully dropped
Enterprise Manager conguration completed successfully
FINISHED EMCA at Nov 22, 2013 1:47:21 PM
Next, assess the database as sysdba and create a ple from the sple.
$ sqlplus / AS SYSDBA
SQL*Plus: Release 11.2.0.3.0 Production on Mon Apr 8 08:53:22 2013
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> create ple from sple;
File created.
SQL> quit
Next, create a directory for the redo log les, as shown in the next example.
$ mkdir /u01/app/oracle/product/redo_logs/
Next, access the Database as sysdba and make either the Eval, Small, Medium, or Large Site initialization parameters, then restart the database.
The following tables show the minimum Oracle Management Repository Database settings for an Eval, Small, Medium and Large Site.
29 of 52
Table 6: Eval Conguration Minimum Database Settings
Parameter
Minimum Value
Processes
300
memory_target
700 MB
redo log le size
50 MB
shared_pool_size
450 MB
session_cached_cursors
remove
Table 7: Small Site Minimum Database Settings

Parameter
Minimum Value
processes
300
pga_aggregate_target*
1024 MB
sga_target*
2 GB
redo log le size
300 MB
shared_pool_size
600 MB
db_securele
PERMITTED
*memory_target of 3 GB can be used in place of sga_target and pga_aggregate_target
Table 8: Medium Site Minimum Database Settings

Parameter
Minimum Value
processes
600
1280 MB
sga_target*
4 GB
redo log le size
600 MB
shared_pool_size
600 MB
db_securele
PERMITTED
*memory_target of 5.25 GB can be used in place of sga_target and pga_aggregate_target
Table 9: Large Site Minimum Database Settings

Parameter
Minimum Value
processes
1000
1536 MB
sga_target*
6 GB
redo log le size
1000 MB
shared_pool_size
600 MB
db_securele
PERMITTED
The next example shows applying the Small Site Oracle Management Repository Database initialization parameters, including force logging, and
adding the redo log les.
Tip: SQL commands to be entered are listed below in BOLD ITALIC.
sqlplus / AS SYSDBA
ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET pga_aggregate_target=1024M SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET sga_target=2G SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET shared_pool_size=600M SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET db_securele=PERMITTED SCOPE=BOTH;
System altered.
ALTER DATABASE force logging;
System altered.
ALTER TABLESPACE users FORCE LOGGING;
System altered.
ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/product/redo_logs/log1c.rdo', '/u01/app/oracle/product/redo_logs/log2c.rdo',
'/u01/app/oracle/product/redo_logs/log3c.rdo') SIZE 100M;
System altered.
SHUTDOWN IMMEDIATE;
SQL> CREATE SPFILE FROM PFILE;
SQL> STARTUP;
ORACLE instance started.
30 of 52
Total System Global Area 3206836224 bytes

Fixed Size
2217632 bytes
Variable Size
1744832864 bytes
Database Buers
1442840576 bytes
Redo Buers
16945152 bytes
Database mounted.
Database opened.
SQL> quit
Automate the Oracle Database Startup and Shutdown

There are several steps to automate the database startup and shutdown process with Oracle Linux.
Once the database has been installed, a le called oratab is created in the /etc directory. The oratab le has a Y/N ag to specify if the database
should be re-started when the server boots.
As root, edit the /etc/oratab le and change N to Y, as shown below.
The default setting is N, as shown in the next example.
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:N
Change the N to Y, as shown in the next example.
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y
The next example shows an oratab le from the above database installation with the Y ag.
# cat /etc/oratab
#
# This le is used by ORACLE utilities. It is created by root.sh
# and updated by the Database Conguration Assistant when creating
# a database.
# A colon, ':', is used as the eld terminator. A new line terminates
# the entry. Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The rst and second elds are the system identier and home
# directory of the database respectively. The third led indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y
Next, as root, create a database startup and shutdown script named dbora /etc/init.d. The dboar script calls the dbstart and dbshut routines.
The next example show the dbora script.
#!/bin/sh
# chkcong: 345 99 10
# description: Oracle auto start-stop script.
#
# Set ORA_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
#
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORA_HOME.
ORA_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORA_OWNER=oracle
if [ ! -f $ORA_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
case "$1" in
'start')
# Start the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME"
31 of 52
touch /var/lock/subsys/dbora
;;
'stop')
# Stop the Oracle databases:
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME"
rm -f /var/lock/subsys/dbora
;;
esac
After the script is created, as root, set the privileges for dbora to 750, by typing:
# chmod 750 /etc/init.d/dbora
The dbora script can now be congured as a Linux service.
Next, as root, set the runlevels for the dbora service to 3, 4 and 5 by typing
# chkcong dbora on
Typing chkcong --list|grep dbora will validate the dbora script is on at runlevels 3, 4 and 5, as shown in the next example.
# chkcong --list|grep dbora
dbora 0:o 1:o 2:on 3:on 4:on 5:on 6:o
Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation Prerequisites

Before starting the Oracle Database 12c Release 1 installation, it is necessary to meet several database, and operating system prerequisites, as well as to download and stage the
software.
Download and Stage the Database Software

Download the Oracle Enterprise Manager 12c R4 software from OTN: http://www.oracle.com/technetwork/database/enterprise-edition/downloads
/index.html
Next, as the installing user, create a directory to stage the software.
$ mkdir -p /u01/stage/db12c
Copy the linuxamd64_12c_database_1of2.zip and linuxamd64_12c_database_2of2.zip les to the staging directory /u01/stage/db12c, then unzip
each le:
$ unzip
linuxamd64_12c_database_1of2.zip
$ unzip
linuxamd64_12c_database_2of2.zip
You should now have a directory called database with the installation les.
$ ll /u01/stage/db12c/
total 2419492
drwxr-xr-x 1 oracle oinstall 110 Jun 10 2013 database
-rw-r--r-- 1 oracle oinstall 1361028723 Jun 16 17:52 linuxamd64_12c_database_1of2.zip
-rw-r--r-- 1 oracle oinstall 1116527103 Jun 16 17:53 linuxamd64_12c_database_2of2.zip
Create the Required Directories using the Optimal Flexible Architecture (OFA)
Standard
The Optimal Flexible Architecture (OFA) standard is a set of le naming recommendations for managing Oracle installations. The Optimal Flexible
Architecture standard oers mount point, directory, and le-naming conventions that work with the Oracle Universal Installer. The Optimal
Flexible Architecture includes where to install each part of each Oracle product including the storage of the applications and the data.
To create the directories for Oracle software installation using the Optimal Flexible Architecture standard, as root, type the following:
# mkdir -p /u01/app/oracle/product/12.1.0/dbhome_1
# chown -R oracle:oinstall /u01/*
# chmod -R 775 /u01/*
Tip: /u01 should be owned by root user
Congure the ulimit, /etc/security/limits.conf and /etc/security/limits.d/oracle-rdbmsserver-12cR1-preinstall.conf Values

One of the Oracle Enterprise Manager 12c installation prerequisites is to increase the number of le descriptors to at least 4096. As root, edit the
/etc/security/limits.conf le and add the following two entries:
<UID> soft nole 4096
<UID> hard nole 4096
If using oracle-rdbms-server-12cR1-preinstall the settings will be in the oracle-rdbms-server-12cR1-preinstall.conf le. As root, edit
the /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf le as shown in the next example.
Change
32 of 52
oracle
To
oracle
soft
nole
1024
soft
nole
4096
There is also a limit on the number of max user processes in the /etc/security/limits.d/90-nproc.conf le. As root, edit the /etc/security/limits.d
/90-nproc.conf le and make the following changes.
Change
* soft nproc 1024
To
* - nproc 16384
Conrm the new limits by looking at output of ulimit -a:
$ su - oracle
$ ulimit -a
core le size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
le size (blocks, -f) unlimited
pending signals (-i) 96073
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open les (-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) 16384
virtual memory (kbytes, -v) unlimited
le locks (-x) unlimited
As the Installing User, Setup ~/.bash_prole

Add the following Oracle variables in the installing user's .bash_prole le as a reference point for your 12c environment.
Add the following to the end of the installing user's ~/.bash_prole le.
Note: Conrm the variable setting for your enviroment. For example, the conrm the bold section above, i.e. paths, the SID, and the unqname.
# Oracle variables
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_HOSTNAME=hostname.domain.com; export ORACLE_HOSTNAME
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/12.1.0/dbhome_1; export ORACLE_HOME
AGENT_HOME=$ORACLE_BASE/product/agentr4/agent_inst; export AGENT_HOME
OMS_HOME=$ORACLE_BASE/product/MiddlewareR4/oms; export OMS_HOME
ORACLE_INSTANCE=/u01/app/oracle/product/gc_inst/WebTierIH1; export ORACLE_INSTANCE
ORACLE_SID=MYSID; export ORACLE_SID
ORACLE_UNQNAME=MYSID; export ORACLE_UNQNAME
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
Next, source the .bash_prole:
$ source ~/.bash_prole
Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation

Tip: ensure you ssh in as the installing user, i.e. oracle, or the graphic installer may not work and give a prerequisite error for display export.
$ cd /u01/stage/db12c/database
$ ./runInstaller
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-06-23_11-54-13AM. Please wait ...
$
Congure Security Updates screen
From the Congure Security Updates screen, to receive security update information from Oracle (optional), enter your email address and My
Oracle Support password and click the Next button, or uncheck the I wish to receive security updates via My Oracle Support checkbox and
click the Next button.
Figure 34
33 of 52
Download Software Updates screen

From the Download Software Updates screen, select one of the following three software update options, then click Next to proceed:
Use My Oracle Support credentials for download
Use pre-downloaded software updates
Skip software updates
For this example we selected Skip software updates then Next to proceed.
Figure 35
Select Installation Option screen

From the Select Installation Option screen select Create and congure a database. Click the Next button to proceed
Figure 36
34 of 52
System Class screen

From the System Class screen select the Server Class option. Click the Next button to proceed.
Figure 37
Grid Installation Options screen

From the Grid Installation Options screen select the Single instance database installation option. Click the Next button to proceed.
Figure 38
35 of 52
Select Install Type screen

From the Select Install Type screen select the Typical Install option. Click the Next button to proceed.
Figure 39
Typical Install Conguration screen

The majority of the settings from the Typical Install Conguration screen for the Typical Install Conguration should autopopulate. For the
settings do not not autopopulate, ensure to enter the following information:
Use the Browse button to select or type in the Oracle base path:
Use the Browse button to select or type in the Software location path:
Storage type: For this example we selcted File system
Use the Browse button to select or type in the Database le location:
Database edition: For this example we selcted Enterprise
OSDBA group: For this example we selcted dba
Enter Global database name: For this example we selcted omr.local.mokumsolutions.com
Administrative password: Enter the administrative password
Conrm password: Conrm the administrative password
For an Oracle Enterprise Manager installation, Create as Container database must be unchecked.
36 of 52
Note: Consult with your DBA to conrm the Install congurations.
Figure 40
Create Inventory screen

From the Create Inventory screen we did not choose to change any defaults options on this screen, Click the Next button to proceed.
Figure 41
Summary screen
From the Summary screen please review the Summary screen to validate your install conguration settings. If changes are necessary use the
Edit links. Once the setting are all veried correct, click the Install button to begin the installation.
Figure 42
37 of 52
Install Product screen

The Install Product screen allows monitoring of the install progress until user input is required.
Figure 43

When presented with the Execute Conguration scripts screen, as the root user open a terminal console and run the requested scripts.
Figure 44
38 of 52
# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete.
# /u01/app/oracle/product/12.1.0/dbhome_1/root.sh
Performing root user operation for Oracle 12c
ORACLE_HOME= /u01/app/oracle/product/12.1.0/dbhome_1
Creating /etc/oratab le...
Finished running generic part of root script.
#
Once the database binaries are in place, the installer launches the Database Conguration Assistant (DBCA). The Database Conguration
Assistant creates the database and shows the installation details, i.e. the log le, Global Database Name, SID and Server Parameter File name are
listed along with the EM Database Express URL for the database. Click the OK button to proceed.
Figure 45
39 of 52
Finish screen
From the Finish screen click Close to nish the database installation
Figure 46
The database has been successfully installed.

If you need to remove the database software, simply run the deinstall utility as follows, respond the the prompts appropriately:
$ORACLE_HOME/deinstall/deinstall
Post Installation Steps

Edit the /etc/oratab le and set restart ag to 'Y.
Change:
omr:/u01/app/oracle/product/12.1.0/dbhome_1:N
To:
omr:/u01/app/oracle/product/12.1.0/dbhome_1:Y
Next, create a directory for Oracle Database redo logs:
$ mkdir /u01/app/oracle/product/redo_logs/
40 of 52
Next, access the database as sysdba and create a ple from the sple ple.
SQL*Plus: Release 12.1.0.1.0 Production on Mon Jun 23 14:31:06 2014
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> create ple from sple;
File created.
SQL> quit
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
$
Next, access the Database as sysdba and make either the Eval, Small, Medium, or Large Site initialization parameters, then restart the database.
The following tables show the minimum Oracle Management Repository Database settings for an Eval, Small, Medium and Large Site.
Table 10: Eval Conguration Minimum Database Settings
Parameter
Minimum Value
Processes
300
memory_target
700 MB
redo log le size
50 MB
shared_pool_size
450 MB
session_cached_cursors
remove
Table 11: Small Site Minimum Database Settings

Parameter
Minimum Value
processes
300
1024 MB
sga_target*
2 GB
redo log le size
300 MB
shared_pool_size
600 MB
db_securele
PERMITTED
*memory_target of 3 GB can be used in place of sga_target and pga_aggregate_target
Table 12: Medium Site Minimum Database Settings

Parameter
Minimum Value
processes
600
1280 MB
sga_target*
4 GB
redo log le size
600 MB
shared_pool_size
600 MB
db_securele
PERMITTED
Table 13: Large Site Minimum Database Settings

Parameter
Minimum Value
processes
1000
1536 MB
sga_target*
6 GB
redo log le size
1000 MB
shared_pool_size
600 MB
db_securele
PERMITTED
The next example shows applying the Small Site Oracle Management Repository Database initialization parameters, including force logging, and
adding the redo log les.
Tip: SQL commands to be entered are listed below in BOLD ITALIC.
sqlplus / AS SYSDBA
ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET pga_aggregate_target=1024M SCOPE=SPFILE;
System altered.
41 of 52
ALTER SYSTEM SET sga_target=2G SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET shared_pool_size=600M SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET db_securele=PERMITTED SCOPE=BOTH;
System altered.
ALTER DATABASE force logging;
System altered.
ALTER TABLESPACE users FORCE LOGGING;
System altered.
SQL> ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/product/redo_logs/log1c.rdo', '/u01/app/oracle/product/redo_logs
/log2c.rdo', '/u01/app/oracle/product/redo_logs/log3c.rdo') SIZE 300M;
Database altered.
SQL> SHUTDOWN IMMEDIATE;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 3791417344 bytes
Fixed Size
2295176 bytes
Variable Size
855640696 bytes
Database Buers
2919235584 bytes
Redo Buers
14245888 bytes
Database mounted.
Database opened.
SQL> quit
$
Next validate that the httpsport is 5500.
SQL*Plus: Release 12.1.0.1.0 Production on Mon Jun 23 15:08:01 2014
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
SQL> SELECT dbms_xdb_cong.gethttpsport FROM dual;
GETHTTPSPORT
-----------5500
SQL> exit
Next, as root, create a database startup and shutdown script named dbora /etc/init.d. The dboar script calls the dbstart and dbshut routines.
The next example show the dbora script.
# cat /etc/init.d/dbora
#!/bin/sh
# chkcong: 345 99 10
# description: Oracle auto start-stop script.
#
# Set ORA_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
#
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORA_HOME.
ORA_HOME=/u01/app/oracle/product/12.1.0/db_1
ORA_OWNER=oracle
if [ ! -f $ORA_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
case "$1" in
'start')
# Start the Oracle databases:
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME"
touch /var/lock/subsys/dbora
;;
'stop')
# Stop the Oracle databases:
42 of 52
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME"
rm -f /var/lock/subsys/dbora
;;
esac
After the script is created, set the privileges for dbora to 750, by typing:
# chmod 750 /etc/init.d/dbora
The dbora script can now be congured as a Linux service.
Next, set the runlevels for the dbora service to 3, 4 and 5 by typing:
# chkcong dbora on
Typing chkcong --list|grep dbora will validate the dbora script is on at runlevels 3, 4 and 5, as shown in the next example.
# chkcong --list|grep dbora
dbora 0:o 1:o 2:on 3:on 4:on 5:on 6:o
The last step is to create soft links for init.d to automate the database startup and shutdown process with Oracle Linux boot process. As root,
type the following commands to create the init.d soft links.
# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S96dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S96dbora
You should test the script by rebooting the machine and validating that the database starts on reboot.
Oracle Enterprise Manager 12c R4 Installation

This section walks through an Advanced installation of the Oracle Enterprise Manager 12c Release 4 (12.1.0.4) Oracle Management Service and
the Oracle Management Agent using the Oracle Universal Installer (OUI) on Oracle Linux 6U5.
Before starting the installation, conrm the RPM prerequisite packages. As root type:
$ yum list make binutils gcc libaio glib-common libstdc++ libXtst systat glibc-devel glibc libaio glibc-devel.i686
Loaded plugins: security
public_ol6_UEKR3_latest | 1.2 kB 00:00
public_ol6_UEKR3_latest/primary | 5.8 MB 00:04
public_ol6_UEKR3_latest 171/171
public_ol6_latest | 1.4 kB 00:00
public_ol6_latest/primary | 39 MB 00:32
public_ol6_latest 25511/25511
Installed Packages
binutils.x86_64 2.20.51.0.2-5.36.el6 @anaconda-OracleLinuxServer-201302251503.x86_64/6.4
gcc.x86_64 4.4.7-4.el6 @ol6_latest
glibc.x86_64 2.12-1.132.el6_5.2 @ol6_latest
glibc-devel.x86_64 2.12-1.132.el6_5.2 @ol6_latest
libXtst.x86_64 1.2.1-2.el6 @anaconda-OracleLinuxServer-201302251503.x86_64/6.4
libaio.x86_64 0.3.107-10.el6 @anaconda-OracleLinuxServer-201302251503.x86_64/6.4
libstdc++.x86_64 4.4.7-4.el6 @ol6_latest
make.x86_64 1:3.81-20.el6 @anaconda-OracleLinuxServer-201302251503.x86_64/6.4
Available Packages
glibc.i686 2.12-1.132.el6_5.2 public_ol6_latest
glibc-devel.i686 2.12-1.132.el6_5.2 public_ol6_latest
libXtst.i686 1.2.1-2.el6 public_ol6_latest
libaio.i686 0.3.107-10.el6 public_ol6_latest
libstdc++.i686 4.4.7-4.el6 public_ol6_latest
$
Install the necessary packages listed under Available Packages.
$ sudo yum install glibc.i686 glibc-devel.i686 libXtst.i686 libaio.i686 libstdc++.i686 -y
As the oracle user make em12104 directory in /u01/stage.
$ mkdir -p /u01/stage/em12104
Download and extract em12104_linux_x64 les to /u01/stage/em12104
$ cd /u01/stage/em12104
$ ll
-rwxrwxr-x 1 oracle oinstall 2195693096 Jun 16 17:49 em12104_linux64_disk1.zip
$ unzip em12104_linux64_disk1.zip
Repeat unzip commands for disk2 and disk3.
As oracle user make directories for oms and agent installs.
$ mkdir -p /u01/app/oracle/product/MiddlewareR4
$ mkdir -p /u01/app/oracle/product/agentr4
Run graphical installer to begin install.
$ ./runInstaller
43 of 52
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-06-24_05-30-24AM. Please wait
$
My Oracle Support Details screen
From the My Oracle Support Details screen to receive information from Oracle (optional), enter your email address and My Oracle Support
password and click the Next button, or uncheck the I wish to receive security updates via My Oracle Support checkbox and click the Next button.
Figure 47
Software Updates screen

From the Software Updates screen select one of the following software update options, then click Next to proceed:
Skip
Search for Updates
Local Directory
My Oracle Support
My Oracle Support (Requires Internet Connection)
User Name
Password
Search for Updates
For this example we selected Skip. Click the Next button to proceed
Figure 48
44 of 52
Prerequisite Checks screen

From the Prerequisite Checks screen the installer checks the system prerequisites. Failed steps can be xed and be retested or just ignored.
The Prerequisite Checks screen shows if the minimum system requirements to perform the installation are met.
Click Rerun if you xed the problems and you would like to verify the system requirements again.
Click Ignore to ignore the problems and move forward with the database installation.
Figure 49
Installation Types screen

From the Installation Types screen select Advanced under Create a new Enterprise Manager System. Click the Next button to proceed.
Figure 50
45 of 52
Installation Details screen

The Installation Details screen should autopopulate, if it does not, enter the following details:
Use the Browse button to select or type in the Middleware Home Location path.
Use the Browse button to select or type in the Agent Base directory path.
The Host Name should auto-populate. If the hostname does not auto-populate, enter the fully qualied domain name (FQDN) of the host.
Figure 51
Select Plug-ins screen

From the Select Plug-ins screen select the desired Plug-ins. Accept the defaults, and to support subsequent chapters of the Oracle Cloud
Cookbook, please select Oracle Cloud Application, Oracle Consolidation Planning and Chargeback and Oracle Virtualization. Click the
Next button to proceed.
46 of 52
Figure 52
WebLogic Server Conguration Details screen

From the WebLogic Server Conguration Details screen enter the WebLogic User Name and Password for the GCDomain and the Node
Manager Password. The OMS Instance Base Location should auto-populate. Click the Next button to proceed.
Tip: The WebLogic and Node Manager passwords can not start with a number.
Figure 53
Database Connection Details screen

From the Database Connection Details screen enter the Database Host Name, the Database Port number, the Database Service/SID, the
Database SYS Password and the Deployment Size. Click the Next button to proceed.
The OEM Deployment sizes are as follows:
47 of 52
Small
Medium
Large
< 100 agents < 1000 targets

< 1000 agents < 10,000 targets
> 1000 agents > 10,000 targets

Figure 54
Enterprise Manager Conguration Details screen

From the Enterprise Manager Conguration Details screen enter the SYSMAN Password and the OMA Agent Registration Password.
Accept the defaults for the Management Tablespace, Conguration Data Tablespace and the IVM Diagnostics Data Tablespace. Click the
Next button to proceed.
Figure 55
Port Conguration Details screen

From the Port Conguration Details screen accept the defaults. Click the Next button to proceed.
48 of 52
Figure 56
Review screen
From the Review screen review the installation setting and continue if correct. Click the Install button to proceed with installation.
Figure 57

From the Installation Progress Details screen you can monitor the progress of the installation until user input is required.
Figure 58
49 of 52

Wehn presented with the Execute Conguration scripts screen, as shown in Figure 59, as the root user, run the allroot.sh script.
# /u01/app/oracle/product/MiddlewareR4/oms/allroot.sh
Starting to execute allroot.sh .........
Starting to execute /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......
Running Oracle 11g root.sh script...
ORACLE_HOME= /u01/app/oracle/product/MiddlewareR4/oms
Finished running generic part of root.sh script.
/etc exist
Creating /etc/oragchomelist le...
/u01/app/oracle/product/MiddlewareR4/oms
Finished execution of /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......
Starting to execute /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......
Finished product-specic root actions.
Finished execution of /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......
#
Finish screen
50 of 52
From the Finish screen your presented with the location of the setupinfo.txt le and the URLs for Oracle Enterprise Manager Cloud Control
and the WebLogic Admin server. Click the Close button to close the installation program
Note: The details from the Finish screen are also available in the le setupinfo.txt le.
Figure 60
The following is an example of the setupinfo.txt le from this install.

$ cat /u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txt
This information is also available at:
/u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
Use the following URL to access:
1. Enterprise Manager Cloud Control URL: https://oem-sisko.local.mokumsolutions.com:7802/em
2. Admin Server URL: https://oem-sisko.local.mokumsolutions.com:7102/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: oem-sisko.local.mokumsolutions.com
2. Admin Server Port: 7102
You can nd the details on ports used by this deployment at : /u01/app/oracle/product/MiddlewareR4/oms/install/portlist.ini
NOTE:
An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the
Repository becomes unusable.
A backup of the OMS conguration is available in /u01/app/oracle/product/gc_inst/em/EMGC_OMS1/sysman/backup on host
oem-sisko.local.mokumsolutions.com. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.
NOTE: This backup is valid only for the initial OMS conguration. For example, it will not reect plug-ins installed later, topology changes like the
addition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensure
they capture the current OMS conguration. Use the following command to backup the OMS conguration:
/u01/app/oracle/product/MiddlewareR4/oms/bin/emctl exportcong oms -dir <backup dir>
The installation is now complete and ready for login
Congure the .bash_prole File with the Oracle Environment Variables (Oracle
11gR2 DB)
After the Oracle Enterprise Manager 12c R4 Installation, add the following Oracle Settings in the /home/oracle/.bash_prole le as a reference
point for your 12c environment.
Note: The following .bash_prole le can be used as is with an all-in-one Oracle Enterprise Manager 12c Installation. For a fresh all-in-one
51 of 52
Oracle Enterprise Manager Cloud Control 12c installation, do not set the Oracle environment until after the installation.
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/app/oracle/product; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/11.2.0/dbhome_1; export ORACLE_HOME
EMDROOT=$ORACLE_BASE/11.2.0/dbhome_1; export EMDROOT
AGENT_HOME=$ORACLE_BASE/agent/agent_inst; export AGENT_HOME
OMS_HOME=$ORACLE_BASE/Middleware/oms; export OMS_HOME
ORACLE_INSTANCE=/u01/app/oracle/product/Middleware/gc_inst/WebTierIH1; export ORACLE_INSTANCE
ORACLE_SID=orcl; export ORACLE_SID
ORACLE_UNQNAME=orcl; export ORACLE_UNQNAME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
52 of 52

Oracle Enterprise Manager 12c Installation 07-16-14

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Oracle Enterprise Manager 12c Installation 07-16-14

Transféré par

Droits d'auteur :

Formats disponibles

Mokum is the only full-time Oracle virtualization

integrator with the expertise to help you virtualize your

Last update: 07/16/14

Oracle Enterprise Manager 12c Release 1 Updates

Oracle Enterprise Manager 12c Release 2 Updates

Oracle Enterprise Manager 12c Release 3 Updates

Oracle Enterprise Manager 12c Release 4 Updates

Oracle Enterprise Manager 12c Installation and Upgrades Introduction

Mokum Solutions, Inc. +1 415 252-9164

Mokum Solutions, Inc. +1 415 252-9164

Enterprise Manager Upload HTTP Port

Enterprise Manager Upload HTTPS (SSL) Port

1159, 4899 - 4908

Management Agent Port

Management Repository Database Port

Cloud Control Console HTTP Port

Cloud Control Console HTTPS (SSL) Port

EM Domain WebLogic Admin Server HTTP Port

EM Domain WebLogic Admin Server HTTPS (SSL)

Mokum Solutions, Inc. +1 415 252-9164

Cloud Control Managed Server HTTP Port

Cloud Control Managed Server HTTPS (SSL) Port

WebLogic Node Manager HTTPS (SSL) Port

JVM Diagnostics Managed Server

JVM Diagnostics Managed Server (SSL)

Application Dependency and Performance RMI

Application Dependency and Performance Java

Application Dependency and Performance Remote

Oracle Enterprise Manager 12c System Design Considerations

Oracle Enterprise Manager 12c Server Sizing

Eval < 10 agents < targets

Small < 100 agents < 1000

Medium < 1000 agents <

Large > 1000 agents >

8 for each RAC

* To use BI Publisher add 1.5 GB of RAM.

MGMT_TABLESPACE (GB) MGMT_ECM_DEPOT_TS (GB) TEMP ARCHIVE LOG AREA (GB)

Eval < 10 agents < targets

Mokum Solutions, Inc. +1 415 252-9164

MGMT_TABLESPACE (GB) MGMT_ECM_DEPOT_TS (GB) TEMP ARCHIVE LOG AREA (GB)

Eval < 10 agents < targets

Oracle Enterprise Manager 12c Release 4 Upgrade

Oracle Database 11 Release 1 (11.1.0.7)

Oracle Database 11g Release 2 (11.2.0.1)

On Linux apply patch 12419378 (Patch Set Update 6).

Oracle Database 11g Release 2 (11.2.0.2)

On Linux apply patch 11061801 and patch 9748749.

Oracle Database 11g Release 2 (11.2.0.3), 10g Release 2

On Linux apply patch 16619249, and patch 13496395.

export ORACLE_SID=<MY SID>

Mokum Solutions, Inc. +1 415 252-9164

Software Updates screen

Mokum Solutions, Inc. +1 415 252-9164

Prerequisite Checks screen

Installation Types screen

Mokum Solutions, Inc. +1 415 252-9164

Installation Details screen

Database Connection Details screen

Mokum Solutions, Inc. +1 415 252-9164

Plug-ins Upgrade screen

Mokum Solutions, Inc. +1 415 252-9164

Select Plug-ins screen

Extend WebLogic Server Domain screen

Mokum Solutions, Inc. +1 415 252-9164