This chapter describes the packages, kernel parameters settings, and libraries required on different platforms (32-bit and 64-bit) for installing a new Enterprise Manager system, an additional Oracle Management Service (OMS), and a standalone Oracle Management Agent (Management Agent).
In particular, this chapter covers the following:
Note:
The packages and libraries are NOT required for Microsoft Windows platforms.This section lists the packages required on different platforms (32-bit and 64-bit) for installing an OMS or a Management Agent. In particular, this section covers the following:
The Enterprise Manager Cloud Control Installation Wizard runs prerequisite checks to verify these packages. If the packages are not found or if the packages are found to be of a lower version than what is required at a minimum, then the wizard prompts you to install the required packages of the required version before proceeding with the installation or upgrade.
The package name contains two parts, mainly the name and the version separated by a hyphen. For example, for libstdc++43-4.3 package, libstdc++43 is the name and 4.3 is the version of the package.
The Enterprise Manager Cloud Control Installation Wizard verifies the package name as well as the version required for a particular platform. For example, if libstdc++43-4.3 is required for SUSE Linux Enterprise 11, and if libstdc++46-4.6.1 is found instead, then the wizard will report this as a missing package and prompt you to install libstdc++43-4.3. This is because libstdc++46-4.6.1 is not a higher version of libstdc++43-4.3; libstdc++46 and libstdc++43 are two different packages (the former is 46 and the latter is 43).
You can have a package of a higher version than what is required, but not a different package and not a package of a lower version. For example, if libstdc++43-4.3 is required for SUSE Linux Enterprise 11, and if libstdc++43-6.7 is found instead, then the wizard will not report this as an issue, and will pass the prerequisite check. This is because, in this case, libstdc++43-6.7 is a higher version of libstdc++43-4.3, which is required at a minimum (the former is 43 and so is the latter).
Therefore, as a prerequisite, make sure you install all the required packages listed in this chapter for your respective platform.
To identify the packages already installed on your system, run the following command. If the command does not list the packages listed in Section 2.1.3 or Section 2.1.4, then install them manually.
rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n" | grep glibc
The command lists all the packages installed on the system. The 32-bit ones are appended with (i386) or (i686), and the 64-bit ones are appended with (x86_64).
For example, if you run the command on a 32-bit system, you should see something similar to the following:
glibc-devel-2.3.4-2.43(i386) glibc-headers-2.3.4-2.43(i386) glibc-2.3.4-2.43(i686) compat-glibc-headers-2.3.2-95.30(i386) glibc-profile-2.3.4-2.43(i386) glibc-utils-2.3.4-2.43(i386) glibc-kernheaders-2.4-9.1.103.EL(i386) glibc-common-2.3.4-2.43(i386) compat-glibc-2.3.2-95.30(i386)
For example, if you run the command on a 64-bit system, you should see something similar to the following:
glibc-common-2.3.4-2.43(x86_64) glibc-devel-2.3.4-2.43(x86_64) glibc-profile-2.3.4-2.43(x86_64) glibc-headers-2.3.4-2.43(x86_64) glibc-utils-2.3.4-2.43(x86_64) glibc-2.3.4-2.43(x86_64)
pkginfo <package_name>
For example,
pkginfo SUNWbtool
lslpp -l <package name>
For example,
lslpp -l bos.perf.proctools
To determine whether a bundle, product, or fileset is installed, enter the following command, where level is either bundle, product, or fileset:
# /usr/sbin/swlist -l level |more
For example,
/usr/sbin/swlist -l bundle |grep QPK
Table 2-1 lists the packages required on different platforms (32-bit and 64-bit) for installing a new Enterprise Manager system or an additional OMS.
Table 2-1 Package Requirements for Oracle Management Service
| Platform | 32-Bit Packages for 32-Bit Platform | 64-Bit Packages for 64-Bit Platform |
|---|---|---|
|
Oracle Linux 7.x Red Hat Enterprise Linux 7 Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 7.2, where 7 is the release number and 2 is the version number. |
Not Supported |
|
|
Oracle Linux 6.x Red Hat Enterprise Linux 6 Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 6.2, where 6 is the release number and 2 is the version number. |
Not Supported |
|
|
SUSE Linux Enterprise 12 |
Not Supported |
|
|
SUSE Linux Enterprise 11 |
Not Supported |
|
|
Solaris SPARC 5.11 |
Not Supported |
|
|
Solaris SPARC 5.10 Also supported on Solaris Local Container |
Not Supported |
SUNWbtool |
|
Solaris x86-64 5.11 |
Not Supported |
|
|
Solaris x86-64 5.10 |
Not Supported |
|
|
IBM AIX 7.1 Note: All maintenance levels are supported. Check the maintenance level using the following command:
|
Not Supported |
|
|
IBM AIX 6.1 Note: All maintenance levels are supported. Check the maintenance level using the following command:
|
Not Supported |
|
|
HP-UX Itanium 11.31 |
Not Supported |
|
Table 2-2 lists the packages required on different platforms (32-bit and 64-bit) for installing a Management Agent.
WARNING:
The GCC packages mentioned in this section are required during installation and also after installation, therefore do not deinstall them after installation. During installation, they are required for relinking binaries, and after installation they are required for discovering hosts and for collecting real-time monitoring modules on Linux hosts. Do NOT deinstall any of the GCC packages after installation.
Table 2-2 Package Requirements for Oracle Management Agent
| Platform | 32-Bit Packages for 32-Bit Platform | 64-Bit Packages for 64-Bit Platform |
|---|---|---|
|
Oracle Linux 7.x Red Hat Enterprise Linux 7 Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 7.2, where 7 is the release number and 2 is the version number. |
Default Packages Are Sufficient |
|
|
Oracle Linux 6.x Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 6.2, where 6 is the release number and 2 is the version number. |
|
|
|
Red Hat Enterprise Linux 6 |
|
|
|
SUSE Linux Enterprise 12 |
Not Supported |
|
|
SUSE Linux Enterprise 11 |
|
|
|
Solaris SPARC 5.11 |
Not Supported |
|
|
Solaris SPARC 5.10 Also supported on Solaris Local Container |
Not Supported |
SUNWbtool |
|
Solaris x86-64 5.11 |
Not Supported |
|
|
Solaris x86-64 5.10 |
Not Supported |
|
|
IBM AIX 7.1 Note: All maintenance levels are supported. Check the maintenance level using the following command:
|
Not Supported |
|
|
IBM AIX 6.1 Note: All maintenance levels are supported. Check the maintenance level using the following command:
|
Not Supported |
|
|
HP-UX Itanium 11.31 |
Not Supported |
OS-Core(B.11.31) |
This section lists the kernel parameters required on different platforms (32-bit and 64-bit) for installing an OMS or a Management Agent. In particular, this section covers the following:
This section covers the following:
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:
# echo 11000 65000 > /proc/sys/net/ipv4/ip_local_port_range
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.
kernel.shmmax Kernel ParameterThis section covers the following:
If OMS and Management Repository Are on Different Hosts
If you are installing OMS and Management Repository (database) on different hosts, which are running on Linux operating systems (32-bit or 64-bit), then on the OMS host, set the kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295.
Oracle recommends this value to avoid lack of memory issues for other applications and to enable a complete and successful core file generation under any and all circumstances.
To verify the value assigned to the kernel.shmmax parameter, run the following command:
cat /proc/sys/kernel/shmmax
To set the value for kernel.shmmax parameter, do the following:
Log in as root.
Open the /etc/sysctl.conf file.
Set the kernel.shmmax parameter to 4294967295.
By setting the value in the /etc/sysctl.conf file, the value persists even when you restart the system. On SUSE Linux Enterprise Server systems, run the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:
# /sbin/chkconfig boot.sysctl on
Run the following command to change the current values of the kernel parameters. Review the output and verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then run this command again.
# /sbin/sysctl -p
Enter the command /sbin/sysctl -a to confirm that the values are set correctly.
After updating the values of the kernel parameters in the /etc/sysctl.conf file, either restart the host, or run the command sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.
If OMS and Management Repository Are on the Same Host
If you are installing OMS and Management Repository (database) on the same host, which is running on a Linux operating system (32-bit or 64-bit), then set the kernel.shmmax parameter to a value prescribed in the Oracle Database Installation Guide that is published for the intended database release and platform.
This section lists the libraries required on different platforms (32-bit and 64-bit) for installing an OMS or a Management Agent. In particular, this section covers the following:
Table 2-3 lists the libraries required on different platforms (32-bit and 64-bit) for installing a new Enterprise Manager system or an additional OMS.
Table 2-3 Library Requirements for Oracle Management Service
| Platform | 32-Bit Libraries for 32-Bit Platform | 64-Bit Libraries for 64-Bit Platform |
|---|---|---|
|
Oracle Linux 7.x Red Hat Enterprise Linux 7.x Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 7.2, where 7 is the release number and 2 is the version number. |
Not Supported |
glibc-2.17 |
|
Oracle Linux 6.x Red Hat Enterprise Linux 6.x Here, x refers to the version of the Oracle Linux release. For example, Oracle Linux 6.2, where 6 is the release number and 2 is the version number. |
Not Supported |
glibc-2.12 |
|
SUSE Linux Enterprise 10 (Service Pack 4) |
Not Supported |
glibc-2.2.4 |
|
SUSE Linux Enterprise 11 |
Not Supported |
glibc-2.11 |