Oracle® Database

3.1 Install libaio Before Installing or Upgrading

Before upgrading to or installing Oracle Database 10g release 2, install the libaio package.

3.2 Install oracleasm-support to use ASMLib

Install oracleasm-support package version 2.0.0.1 or later to use ASMLib on Oracle Enterprise Linux 4.0, Red Hat Enterprise Linux 4.0 Advanced Server, or SUSE Linux Enterprise Server 9. At the time of this publication, the ASMLib user space tools and kernel module packages are not yet available for SUSE Linux Enterprise Server 10.

3.3 Oracle HTTP Server on Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0

If you intend to use Oracle HTTP server, which is included in Companion CD of Oracle Database 10g Release 2 (10.2) Media pack, refer to the MetaLink note 317085.1 for more information on using Oracle HTTP server on Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0 .

3.4 Oracle HTTP Server on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0

If you intend to use Oracle HTTP server, which is included in Companion CD of Oracle Database 10g Release 2 (10.2) Media pack, refer to the MetaLink note 317085.1 for more information on using Oracle HTTP server on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0.

Legacy entry points required by this version of Apache (libdb.so.2) are moved to gdbm-1.8.0-26.2.1.i386. You must create a symlink using the following command:

$ ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

3.5 Configuring Kernel Parameters

After updating the values of kernel parameters in the /etc/sysctl.conf file, ensure that you either reboot the computer or run the sysctl -p command to make the changes of the /etc/sysctl.conf file available in the active kernel memory.

On SUSE Linux Enterprise Server 9.0, ensure that you set the following kernel parameter:

disable_cap_mlock = 1

On SUSE Linux Enterprise Server 10, ensure that you set the hugetlb_shm_group kernel parameter to the GID of the group used as the dba group. For example, on a system using a group named dba with the dba:!:104:oracle entry in the /etc/group file, the hugetlb_shm_group kernel parameter should be set to the following value:

hugetlb_shm_group = 104

4.1 Latest Upgrade Information

For late-breaking updates and best practices about preupgrades, postupgrades, compatibility, and interoperability discussions refer to note 466181.1 on OracleMetaLink (https://metalink.oracle.com/) that links to "The Upgrade Companion" Web site.

4.2 Upgrading Oracle Real Application Clusters Release 9.2

If you are upgrading a 9.2 RAC environment to Oracle Database 10g release 2 on Red Hat Linux 3.0, then you must apply a patch to GLIBC before proceeding with the Oracle Clusterware installation. Follow the instructions documented in OracleMetaLink note 284535.1.

This issue is tracked with Oracle bug 3006854.

4.3 Oracle Universal Installer Operating System Prerequisite Checks

If you are installing Oracle Database 10g on Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 5.0, or SUSE Linux Enterprise Server 10, the current version of Oracle Universal Installer does not recognized these operating systems as supported operating systems and does not perform the installation.

Workaround #1 (recommended): Run the Oracle Universal Installer using the ignoreSysPrereqs flag which causes the installer to skip the operating system check and continue with the installation:

./runinstaller -ignoreSysPrereqs

As a side effect, the installer also skips other checks during the installation.

Workaround #2: On Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0, the installation passes the operating system prerequisite checks if you change each 5 to 4 in the /etc/redhat-release file. Ensure that you replace the original values in the /etc/redhat-release file after the Oracle installation is complete.

On SUSE Linux Enterprise Server 10, the installation will pass the operating system prerequisite checks if you change each 10 to 9 in the /etc/SuSE-release file. Ensure that you replace the original values in the /etc/SuSE-release file after the Oracle installation is complete.

This workaround causes Oracle Universal Installer to consider the system to be running earlier version of the operating system and the operating system check passes. The changes to the release file should be reverted after the installation of all Oracle software is complete. The changes to the release file could impact the ability of other tools to be properly installed on the operating system.

4.4 Installing Oracle Cluster Ready Services

Near the end of the installation of Oracle Cluster Ready Services, Oracle Universal Installer prompts for the $CRS_HOME/root.sh script to be run on all of the nodes in the cluster. When the root.sh script is run on the last node in the cluster, the script calls the VIPCA utility, which fails on Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 5.0, and SUSE Linux Enterprise Linux 10. Refer to the "SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter" section for more details.

Workaround: Before running the root.sh script on the last node in the cluster, alter the $CRS_HOME/bin/vipca script commenting out lines 119 through 123:

arch='uname -m'
#       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]
#       then
#            LD_ASSUME_KERNEL=2.4.19
#            export LD_ASSUME_KERNEL
#       fi

With the lines commented out, root.sh should be able to call VIPCA successfully. Ensure that you do not comment out line 118, which sets the arch variable as that is needed by the root.sh script.

4.5 Adding a Node to a Shared Oracle Clusterware Configuration

Before running root.sh in the first node of a shared Oracle Clusterware home, add the following line in the $ORA_CRS_HOME/opmn/conf/ons.config file:

usesharedinstall=true

This issue is tracked with Oracle bug 4454562.

4.6 Installing Enterprise Security Manager

To install Oracle Security Manager, install Oracle Client and then select the Administrator installation type.

4.7 Upgrading Oracle Clusterware 10.1.x to Oracle Clusterware 10.2

When upgrading from 10.1.x to 10.2, Oracle Clusterware will not start if the host name directory under the /etc/oracle/scls_scr directory includes the domain name. The following error message is displayed when you run the rootupgrade.sh script.

A file or directory in the path name does not exist. /etc/init.cssd[509]:
/etc/oracle/scls_scr/host_name/root/cssrun: 0403-005Cannot create the specified file.

Workaround: Move the /etc/oracle/scls_scr/hostname.domain_name directory to /etc/oracle/scls_scr/hostname and rerun the rootupgrade.sh script.

Oracle recommends that you should apply the latest release of the Oracle Clusterware patch.

This issue is tracked with Oracle bug 4472284.

4.8 extjob Executable Required Directory Permissions

To enable the extjob executable to locate required libraries, the $ORACLE_HOME/lib directory and all of its parent directories must have execute permissions for group and other.

4.9 Modifying a Virtual IP Address Node Application

Use the srvctl modify nodeapps command to modify the name, IP address, or netmask of an existing virtual IP address (VIP) resource. Use the -A argument to include the existing interfaces for the VIP:

srvctl modify nodeapps -n mynode1 -A 100.200.300.40/255.255.255.0/eth0

This issue is tracked with Oracle bug 4500688.

4.10 Raw Devices on Oracle Enterprise Linux and Red Hat Enterprise Linux

When you restart an Oracle Enterprise Linux 4.0, Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 4.0, or Red Hat Enterprise Linux 5.0 system, raw devices revert to their original owners and permissions by default. If you are using raw devices with this operating system for the Oracle files, for example, for ASM storage or Oracle Clusterware files, you need to override this default behavior. To do this, add an entry to the /etc/rc.d/rc.local file for each raw device containing the chmod and chown commands required to reset them to the required values.

As an example, here are sample entries in a /etc/rc.d/rc.local file that control the restart behavior of raw devices for two ASM disk files (/dev/raw/raw6 and /dev/raw/raw7), two Oracle Cluster Registry files (/dev/raw/raw1 and /dev/raw/raw2), and three Oracle Clusterware voting disks (/dev/raw/raw3, /dev/raw/raw4, and /dev/raw/raw5):

# ASM
chown oracle:dba /dev/raw/raw6
chown oracle:dba /dev/raw/raw7
chmod 660 /dev/raw/raw6
chmod 660 /dev/raw/raw7
# OCR
chown root:oinstall /dev/raw/raw1
chown root:oinstall /dev/raw/raw2
chmod 660 /dev/raw/raw1
chmod 660 /dev/raw/raw2
# Voting Disks
chown oracle:oinstall /dev/raw/raw3
chown oracle:oinstall /dev/raw/raw4
chown oracle:oinstall /dev/raw/raw5
chmod 644 /dev/raw/raw3
chmod 644 /dev/raw/raw4
chmod 644 /dev/raw/raw5

4.11 Oracle Cluster Ready Services Daemon fails on Computer Restart

If different user IDs are used for installing Oracle Database 10g and Oracle Clusterware, then restarting the system results in OCR errors. Refer to the OracleMetaLink note 551478.1 for more information.

Workaround: Oracle recommends that you apply patch set 10.2.0.3 or higher to Oracle Clusterware install before patching Oracle Database.

This issue is tracked with the Oracle bug 4748946.

4.12 Error When Installing Oracle Database 10g on Asianux Server 3

When installing Oracle Database 10g on Asianux Serever 3, the Product Specific Prerequisite Checks screen reports that the operating system requirement checks fail.

Workaround: Change the contents of /etc/asianux-release from Asianux Server 3 (Quartet) to Asianux release 3 (Quartet).

This issue is tracked with the Oracle bug 6388770.

4.13 Configuring Storages Devices for Oracle Clusterware on 2.6 Kernel Distributions

This section is for database and system administrators who intend to install or migrate to Oracle10g Release 2 (10.2.0) RAC on Red Hat Enterprise Linux 5 (RHEL5) or Oracle Enterprise Linux 5 (OEL5), and who need to configure raw devices for Oracle RAC and Oracle Clusterware. The Linux 2.6 kernel with these distributions requires additional configuration steps. The section contains the following topics:

• Overview of Device Naming Persistence Changes

• Configuring Raw Devices for Clusterware on Red Hat and Oracle Enterprise Linux 5

• Relocate Oracle Clusterware Files from Raw to Block Devices

5.1 Building Pro*C Applications if PostgreSQL is Installed

If the postgresql-devel package is installed on the system, then you must add the following directory to the beginning of the sys_include parameter in the $ORACLE_HOME/precomp/admin/pcscfg.cfg file before building Pro*C applications:

$ORACLE_HOME/precomp/public

If you do not make this change, then you may encounter errors similar to the following when linking the applications:

/tmp/ccbXd7v6.o(.text+0xc0): In function `drop_tables': 
: undefined reference to 'sqlca'

This issue is tracked with Oracle bug 3933309.

5.2 Encoding Information Not Present in Translated Help Files

If the system uses a European language, you might see corrupted characters in Table of Contents of database tools, such as Database Configuration Assistant.

This issue is tracked with Oracle bug 3957096.

Workaround: If the system uses a European language, do not use the .UTF-8 locale. For example, if the system uses German, set the LANG and LC_ALL environment variables to de_DE instead of de_DE.UTF-8.

5.3 Oracle Clusterware Files Issues

The following note applies if you are using Oracle Enterprise Linux 4.0, Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 4.0, Red Hat Enterprise Linux 5.0, or SUSE Linux Enterprise Server 10 and using raw devices to store the Oracle Cluster Registry (OCR) and the voting disk for Oracle Clusterware, or using raw devices for Automatic Storage Management (ASM) database files. For each raw device used for the purposes listed, you must add two entries in the /etc/rc.d/rc.local file on Oracle Enterprise Linux 4.0, Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 4.0, and Red Hat Enterprise linux 5.0, or the /etc/init.d/after.local file on SUSE Linux Enterprise Server 10 after running the root.sh script following the installation of Oracle Clusterware.

For each OCR file, the entries should look as follows, where oinstall is the Oracle install group and /dev/raw/rawn is an individual device file:

chown root:oinstall /dev/raw/rawn
chmod 660 /dev/raw/rawnmar

For each voting disk file, the entries should look as follows, where oracle is the Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an individual device file:

chown oracle:oinstall /dev/raw/rawn
chmod 644 /dev/raw/rawnmar

For each ASM file, the entries should look as follows, where oracle is the Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an individual device file:

chown oracle:oinstall /dev/raw/rawn
chmod 660 /dev/raw/rawnmar

5.4 VLM Window Size on Oracle Enterprise Linux and Red Hat Enterprise Linux

To use hugepages or to accommodate the VLM window size on Oracle Enterprise Linux 4.0, Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 4.0, or Red Hat Enterprise Linux 5.0, you must increase the default maximum size of the per-process locked memory. To increase the per-process max locked memory limit, add the following lines to the /etc/security/limits.conf file, where oracle is the user that administers the database:

oracle soft memlock 3145728
oracle hard memlock 3145728

5.5 Oracle XML Developer's Kit Compiler Support

On Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0, Oracle XML Developer's Kit (XDK) is not supported with GCC. XDK is supported with Intel C++ compiler (ICC).

5.6 Removing Metrics for Wait Classes Removes Them Permanently

Do not remove the key values for the wait class metrics. Doing so removes them permanently and currently there is no easy way to recover them.

This issue is tracked with Oracle bug 4602952.

5.7 SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter

The SRVCTL and VIPCA utilities shipped with Oracle Database 10g release 2 and Oracle Clusterware software set the environmental variable LD_ASSUME_KERNEL. On Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 5.0, and SUSE Linux Enterprise Server 10, because the older Linux threads API has been removed from GLIBC, setting this parameter causes the SRVCTL and VIPCA utilities to exit with the following error:

/opt/oracle/crs/jdk/jre/bin/java: 
error while loading shared libraries: 
libpthread.so.0: cannot open shared object file:
No such file or directory

Workaround: Comment out the lines that set the LD_ASSUME_KERNEL variable from the VIPCA and SRVCTL utilities. For the VIPCA utility alter the $CRS_HOME/bin/vipca script commenting out lines 119 through 123 as follows:

arch='uname -m'
#       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]
#       then
#            LD_ASSUME_KERNEL=2.4.19
#            export LD_ASSUME_KERNEL
#       fi

With the lines commented out, root.sh should be able to call VIPCA successfully. Ensure that you do not to comment out line 118 which sets the arch variable as that is needed by the script.

For the SRVCTL utility alter the $CRS_HOME/bin/srvctl and the $ORACLE_HOME/bin/srvctl scripts commenting out lines 173 and 174 as follows:

#Remove this workaround when the bug 3937317 is fixed
#LD_ASSUME_KERNEL=2.4.19
#export LD_ASSUME_KERNEL

5.8 Mapping of 127.0.0.2 to the Local Hostname

By default, the hostname of a machine is mapped to the IP address 127.0.0.2 through an entry in the /etc/hosts similar to the following on SUSE Linux Enterprise Server 10:

127.0.0.2       test test.example.com

YaST does this to provide compatibility with earlier versions of the applications that had problems running on desktops with dynamically assigned hostnames from DHCP. This mapping may cause certain Oracle networking libraries to encounter errors when they attempt to resolve the hostname of the machine. To avoid these problems, the entry should be removed from the /etc/hosts file. Note that several network related YaST utilities may add this entry back to the file.

The hostname must be included in the /etc/hosts file. if you do not include the hostname in this file, then the following error is displayed:

ORA-00600: internal error code, arguments: [keltnfy-ldmInit],[46],[1],[],[],[],[],[]

5.9 Error While Loading Shared Library When selinux is Enabled on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0

Oracle Call Interface (OCI) program calls fail with selinux enabled on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0.

Workaround: Disable selinux on the system.

This issue is tracked with Oracle bug 6079461.

5.10 Linking Applications With Oracle Client Libraries

The use of the client static library is not supported.

5.11 MAX_IDLE_BLOCKER_TIME Does Not Work in Oracle RAC Environment

Setting a value for MAX_IDLE_BLOCKER_TIME feature of Resource manager does not work as expected in Oracle RAC environment.

Workaround: Set a value for MAX_IDLE_TIME instead of setting a value for MAX_IDLE_BLOCKER_TIME.

This issue is tracked with Oracle bug 6114355.

5.12 Database Control Does not Display the Listener Details

When you connect to the database using Database Control, the page does not display the listener details.

Workaround: After installing Oracle Database 10g release 2, you must shutdown the Database Control with the command emctl stop dbconsole. Modify the targets.xml file located in $ORACLE_HOME/hostname_SID/sysman/emd directory so that the value of the machinename field is the same for listener and database. Restart Database Control with the command emctl start. dbconsole to display the listener details.

This issue is tracked with Oracle bug 6743916.

6.1 Extracting Installation Files

The "Extracting the Installation Files" section in chapter 3 of the installation guides, lists the steps for extracting files from a gz archive. However, the installation files available on Oracle Technology Network are in zip archive format.

To extract files from the zip archive, use the following command:

$ unzip filename.zip

6.2 Incorrect CRS Home Example

In Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide, Chapter 2, "Preinstallation," in the section "Oracle Clusterware Home Directory," it incorrectly lists the path /u01/app/oracle/product/crs as a possible Oracle Clusterware home (or CRS home) path. This is incorrect. A default Oracle base path is /u01/app/oracle, and the Oracle Clusterware home must never be a subdirectory of the Oracle base directory.

A possible CRS home directory is in a path outside of the Oracle base directory. for example, if the Oracle base directory is u01/app/oracle, then the CRS home can be an option similar to one of the following:

u01/crs/
/u01/crs/oracle/product/10/crs
/crs/home

This issue is tracked with Oracle bug 5843155.

6.3 List of Packages for Asianux 2.0, Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0

In the "Software Requirements" section of quick installation guides and Chapter 2 of installation guides, the following (or later versions) are the list of packages for Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0:

binutils-2.15.92.0.2-18
compat-libstdc++-33.2.3-47.3
elfutils-libelf-0.97-5
elfutils-libelf-devel-0.97-5
gcc-3.4.5-2
gcc-c++-3.4.5-2
glibc-2.3.4-2.19
glibc-common-2.3.4-2.19
glibc-devel-2.3.4-2.19
glibc-headers-2.3.4-2.19
libaio-devel-0.3.105-2
libaio-0.3.105-2
libgcc-3.4.5
libstdc++-3.4.5-2
libstdc++-devel-3.4.5-2
make-3.80-5
sysstat-5.0.5
unixODBC-2.2.11
unixODBC-devel-2.2.11

6.4 List of Packages for Asianux 3.0, Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0

The following packages (or later versions) are supported on Oracle Database 10g release 2:

binutils-2.17.50.0.6-2.el5
compat-libstdc++-33-3.2.3-61
elfutils-libelf-0.125-3.el5
elfutils-libelf-devel-0.125
gcc-4.1.1-52
gcc-c++-4.1.1-52
glibc-2.5-12
glibc-common-2.5-12
glibc-devel-2.5-12
glibc-headers-2.5-12
libaio-0.3.106
libaio-devel-0.3.106 
libgcc-4.1.1-52
libstdc++-4.1.1 
libstdc++-devel-4.1.1-52.e15
make-3.81-1.1
sysstat-7.0.0
unixODBC-2.2.11
unixODBC-devel-2.2.11

6.5 List of Packages for SUSE Linux Enterprise Server 10

The following packages (or later versions) are supported on Oracle Database 10g release 2:

binutils-2.16.91.0.5
compat-libstdc++-5.0.7
gcc-4.1.0
glibc-2.4-31.2
glibc-devel-2.4-31.2
ksh-93r-12.9
libaio-0.3.104
libaio-devel-0.3.104
libelf-0.8.5
libgcc-4.1.0
libstdc++-4.1.0
libstdc++-devel-4.1.0
make-3.80
sysstat-6.0.2
unixODBC-2.2.11
unixODBC-devel-2.2.11

6.6 Oracle Clusterware and Oracle RAC Virtual IP Address Status

The following text of the section 2.6.1, "IP Address Requirements," in Chapter 2, "Pre-Installation Tasks," of Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide states that the virtual IP address (VIP) should respond to a ping command:

During installation, Oracle Universal Installer uses the ping command to ensure that the VIP is reachable.

The preceding statement is incorrect. Before installation, the VIP address should be configured in DHCP or /etc/hosts, or both, but it must not be assigned to a server that can respond to a ping command.

This issue is tracked with Oracle bug 6017001.

6.7 Incorrect Value for MAXINSTANCES

Appendix H, "Database Limits" of Oracle Database Administrator's Reference for UNIX-Based Operating Systems states the incorrect maximum value (63) for the MAXINSTANCES variable. The correct maximum limit for the variable is 1055.

6.8 The hangcheck_reboot Parameter on Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0

The following is an additional information to the section 2.16, "Checking the Configuration of the Hangcheck-timer Module" of Chapter 2, "Pre-Installation Tasks" in Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux. This information is related to the hangcheck_reboot parameter in Oracle Enterprise Linux 4.0 and Red Hat Enterprise Linux 4.0.

The hangcheck_reboot parameter determines if the hangcheck-timer restarts the node if the kernel fails to respond within the sum of the hangcheck_tick and hangcheck_margin parameter values. If the value of hangcheck_reboot is equal to or greater than 1, then the hangcheck-timer module restarts the system. Using the default values, the node would be restarted if the kernel fails to respond within 240 seconds. If the hangcheck_reboot parameter is set to zero, then the hangcheck-timer module is suspended.

For optimal cluster performance, test applications with the hangcheck parameter values that Oracle recommends. If you find that the cluster produces false node evictions with these values, then increase the parameter values, and retest the cluster.

6.9 The noac option for NFS May not Work as Expected

In the "NFS Mount Options" section of Appendix C, "Using NAS Devices" in Oracle Database Installation Guide 10g Release 2 (10.2) for Linux x86 the table should also contain the following entry:

6.10 Package Missing for SUSE Linux Enterprise Server 9

The db1-1.85-85.1 package is missing from the list for packages for SUSE Linux Enterprise Server 9 in Oracle Database Companion CD Installation Guide 10g Release 2 for Linux x86.

6.11 Incorrect Kernel Parameter Values

Chapter 2, "Oracle Database Preinstallation Requirements" of Oracle Database Installation Guide for Linux x86 states the incorrect value for shmmax parameter. The correct limit for the kernel is minimum of the following values:

• Half the size of the memory

• 4GB - 1 byte

6.12 Additional Kernel parameters

The following Kernel parameters should be added to Chapter 2, "Oracle Database Preinstallation Requirements" of Oracle Database Installation Guide for Linux x86:

• The table listing the recommended values for the kernel parameters in the section should contain the following rows:

  Parameter	Minimum Value	File
  tcp_wmem	262144	/proc/sys/net/ipv4/tcp_wmem
  tcp_rmem	4194304	/proc/sys/net/ipv4/tcp_rmem

  
  

• The table listing the commands to display the values of the kernel parameters in the section should contain the following rows:

  Parameter	Command
  tcp_wmem	# /sbin/sysctl -a | grep tcp_wmem
  tcp_rmem	# /sbin/sysctl -a | grep tcp_rmem

  
  

• The list of parameters and their values in the /etc/sysctl.conf file should also contain the following entries:

  net.ipv4.tcp_wmem = 262144 262144 262144
  net.ipv4.tcp_rmem = 4194304 4194304 4194304
  

6.13 Oracle Clusterware Process Monitor Daemon replaces Hangcheck Timer

Oracle Clusterware for 10.2.0.4 on Linux Red Hat and SUSE now uses the Oracle Clusterware Process Monitor Daemon (oprocd) to monitor the system state of the cluster nodes.

Refer to the Red Hat Enterprise Linux or SUSE Linux Enterprise Server distribution documentation for further information about oprocd.