Oracle Management Agent : Table 3-2 Package Requirements

WARNING:

3.2.1.1 Verifying UDP and TCP Kernel Parameters

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 65500 > /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.

3.1.4 Package Requirements for Oracle Management Agent

• Ensure that you install only the versions recommended in Table 3-2. Installing any lower or higher versions of the packages might cause the installation to fail.
• 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.
   CHECK installed packaged by
  
  #rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n" | grep glibc
 
  compat-glibc-2.12-4.el7(x86_64)
  glibc-2.17-78.0.1.el7(i686)
  glibc-common-2.17-78.0.1.el7(x86_64)
  glibc-headers-2.17-78.0.1.el7(x86_64)
  glibc-devel-2.17-78.0.1.el7(x86_64)
  compat-glibc-headers-2.12-4.el7(x86_64)
  glibc-devel-2.17-78.0.1.el7(i686)
  glibc-2.17-78.0.1.el7(x86_64)
  
  

  Table 3-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 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	make-3.82-21 binutils-2.23.52.0.1-16 gcc-4.8.2-16 libaio-0.3.109-12 glibc-common-2.17-55 libstdc++-4.8.2-16 sysstat-10.1.5-4

  3.2.1.2 Setting Up kernel.shmmax Kernel Parameter

  This section covers the following:
  

  • If OMS and Management Repository Are on Different Hosts
  • If OMS and Management Repository Are on the Same Host

  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:
    
    1. Log in as root.
    2. Open the /etc/sysctl.conf file.
    3. 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, do the following:
    
    1. Run the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:
       # /sbin/chkconfig boot.sysctl on
       
    2. Run the following command to change the current values of the kernel parameters:
       # /sbin/sysctl -p
       

  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 11g Release 2 (11.2) for Linux.