Escolar Documentos
Profissional Documentos
Cultura Documentos
This brief document describes the high-level goals and scope for installing Oracle Enterprise
Manager 13c Release 2.
Also included are the known prerequisites for installing Oracle Enterprise Manager 13c into a
Solaris SPARC 5.11 (64-bit) server to act as the management server. The management server will
host both the Oracle Enterprise Manager server and the corresponding databases.
The prerequisites in this document are expected to cover most eventualities, but as with any
installation procedure, further detail and additional information may be required.
Scope
Install a standard Oracle Enterprise Manager 13c Cloud Control server onto a Solaris SPARC 5.11
(64-bit) host.
Prerequisites
This section details what will be required for the installation of Oracle Enterprise Manager 13c
Cloud Control server.
These are the prerequisites for installing the below components on one SPARC (64-bit) 11
Systems server:
CPU, RAM, Heap Size, and Hard Disk Space Requirements for Oracle Management
Service
CPU, RAM, and Hard Disk Space Requirements for Oracle Management Repository
The following packages must be installed on the Solaris Solaris SPARC 5.11 (64-bit) management
server to facilitate OEM 13c OMS:
SUNWbtool
SunWhea or system/header
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWxwplt (This is for setting xwindow)
SUNWfont-xorg-core (This package is required only for GUI-based interactive installation, and
not for silent installation)
SUNWlibC
SUNWcsl
Use the Oracle Database prerequisites group package to simplify operating system configuration
and to ensure that you have the required packages.
Starting with Oracle Solaris 11.2, for Oracle Database 12c Release 1 (12.1) and later databases, use
the Oracle Database prerequisites group package group/prerequisite/oracle/oracle-rdbms-
server-12-1-preinstall to ensure that all the necessary packages required for an Oracle Database
and Oracle Grid Infrastructure installation are present on the system.
You can install oracle-rdbms-server-12-1-preinstall even if you installed Oracle Solaris using any
of the server package groups, such as solaris-minimal-server, solaris-small-server, solaris-large-
server, or solaris-desktop.
Configuring a server using Oracle Solaris and the Oracle Database prerequisites group package
consists of the following steps:
Set TCP/IP ephemeral port range parameters to provide enough ephemeral ports for the
anticipated server workload. Ensure that the lower range is set to at least 11,000 or higher, to
avoid Well Known ports, and to avoid ports in the Registered Ports range commonly used by
Oracle and other server ports.
Set the port range high enough to avoid reserved ports for any applications you may intend to
use. If the lower value of the range you have is greater than 11,000, and the range is large enough
for your anticipated workload, then you can ignore OUI warnings regarding the ephemeral port
range.
For example, with IPv4, use the following command to check your current range for ephemeral
ports:
$ cat /proc/sys/net/ipv4/ip_local_port_range
32768 61000
In the preceding example, the lowest port (32768) and the highest port (61000) are set to the
default range.
If necessary, update the UDP and TCP ephemeral port range to a range high enough for
anticipated system workloads, and to ensure that the ephemeral port range starts at 11,000 and
above.
For example:
Oracle recommends that you make these settings permanent. For example, as root, use a text
editor to open /etc/sysctl.conf, and add or change to the following: net.ipv4.ip_local_port_range
= 11000 65500, and then restart the network (# /etc/rc.d/init.d/network restart). For detailed
information on how to automate this ephemeral port range alteration on system restarts, refer to
your Linux distribution system administration documentation.
Ensure that the maximum user process limit is set to 13312 or greater. However, do not set it to
unlimited.
To verify the current value that is set, run the following command:
ulimit -u
To verify whether it is set to unlimited, run the following command. If it is set to unlimited, the
output will be unlimited.
If the current value is not set to 13312 or greater, or if it is set to unlimited, then contact your
system administrator to correct it.
Ensure that you set the soft limit of the file descriptor to a minimum of 4096 and the hard limit to
less then or equal to 16384.
If the current value is not 4096 or greater, then as a root user, update the etc/security/limits.conf
file with the following entries:
For example,
According to RFC 952, the following are the assumptions: A name (Net, Host, Gateway, or
Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9),
minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit
components of domain style names. No blank or space characters are permitted as part of a
nslookup myhost
nslookup myhost.example.com
nslookup 172.16.0.0
If alias host names are implemented in /etc/hosts, then it is not necessary to be able to use DNS
to resolve the alias host name on which you want to install the OMS.
Ensure the following user and group are created on the RHEL management server:
Owner of the installation – oracle
Default group for the oracle user – oinstall
The 'oracle' user must have write access to the location to be used to store the OEM instance and
the OMS file store.
The Oracle Universal Installer used to install Oracle Enterprise Manager is a graphical utility that
employs X-Windows. The management server must support X-Windows applications and the
workstation from where the installation will be performed must support X-Windows access.
In the event that an internet proxy is used to grant Oracle Enterprise Manager 13c access to the
public internet to facilitate product downloads and updates, ensure the proxy provides access to
the following sites:
aru-akam.oracle.com
ccr.oracle.com
login.oracle.com
support.oracle.com
updates.oracle.com
Also ensure that the proxy server allows HTTPS connections to those sites above and gather the
following information for configuring OEM:
proxy server host name for HTTPS
connection port number
username, password and realm if these security features are used
The default upload port for Management Agent is 3872. The same port is used for both
HTTP and HTTPS. If 3872 is not available, then the first available free port from the range
1830 to 1849 is selected.
Administration Server
Node Manager
The default HTTPS port is the first available free port from the range 7401 to 7500 is
selected.
Managed Server
The default HTTP port is the first available free port from the range 7201 to 7300 is
selected.
The default HTTPS port is the first available free port from the range 7301 to 7400 is
selected.
If SLB is not configured, then the aforementioned HTTP and HTTPS upload ports of
Enterprise Manager Cloud Control are used. If SLB is configured, then the ports
configured for JVM Diagnostics on the SLB are used. Alternatively, in addition to the SLB
configuration, if the HTTP upload port is enabled for Enterprise Manager Cloud Control,
then the HTTP upload port also can be used by the JVM Diagnostics Agents for
communicating with the JVM Diagnostics Engine.
Oracle BI Publisher
The default HTTP port for Oracle BI Publisher is 9701. If 9701 is not available, then the
first available free port from the range 9701 to 9750 is selected.
The default HTTPS port for Oracle BI Publisher is 9801. If 9801 is not available, then the
first available free port from the range 9801 to 9850 is selected.
The default HTTP port for Oracle HTTP Server is 9788. If 9788 is not available, then the
first available free port from the range 9751 to 9800 is selected.
The default HTTPS port for Oracle HTTP Server is 9899. If 9899 is not available, then the
first available free port from the range 9851 to 9900 is selected.
The default JOC port is 23456. If 23456 is not available, no alternate port is used, so
ensure that port 23456 is free.
The Enterprise Manager OMS server(s) require direct network access to each of the targets
servers. If the names of the target server are not registered in the OMS nodes' DNS, then they
will have to be manually entered in the /etc/hosts file for the OMS host.
Each target server should be verified to be able to resolve the hostnames of the OMS server and
vise versa. Again, if the names of target servers are not registered in DNS, then entries can be
added to the /etc/hosts file of each target server.
1. Allow ping
In many secure network environments, it is normal for the ping service to be disabled.
Enterprise Manager uses ping to establish the basic availability and status of the Exadata
Database Machine components.
The database listener ports must be opened for the Enterprise Manager OMS server.
The Enterprise Manager Cloud Control 13c agents require access to the Enterprise
Manager Servers upload service.
The OMS server(s) will need to be able to connect to the Enterprise Manager Cloud
Control 13c Agent HTTP/HTTPS port on each target server. The Agent port defaults to
3872.